search

kubernetes-sigs / application

Application metadata descriptor CRD
Apache License 2.0
513 stars 167 forks source link

Dear Google, how do I contribute to this project? Are you abandoning the Application CRD? #223

Closed borgilb closed 1 year ago

borgilb commented 2 years ago

I being dramatic to try to get some response here :)

I really like the Application CRD and want to keep using it. I know Google is the only one driving its development. Its officially supported by the GKE UI and from what I have heard possible future GKE features might use it? But this github project is dead. I want to open issues and PRs, but no one is looking at this.

I'd like to know sooner rather than later if Google is abandoning it.

Thanks!

vikramspringml commented 2 years ago

Same question here ? Any updates Googlers?

borgilb commented 2 years ago

I've been lead to believe its not being deprecated inside Google at least.

I will say though I really love this project and would like to contribute, if not code, issues and feature requests.

RainbowMango commented 2 years ago

Its officially supported by the GKE UI and from what I have heard possible future GKE features might use it?

@borgilb Any links to the GKE UI? I'm interested in this project too.

red8888 commented 2 years ago

@RainbowMango https://cloud.google.com/solutions/using-gke-applications-page-cloud-console

RainbowMango commented 2 years ago

Thanks @red8888

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

nuclearwu commented 2 years ago

Thanks @red8888

Hi @RainbowMango ，Is it possible to integrate some concepts of this project about applications into karmada to achieve application distribution and management across multiple clusters

RainbowMango commented 2 years ago

Yeah, I was thinking about it. The concepts of this project are great.

/remove-lifecycle stale

borgilb commented 2 years ago

@nuclearwu not really. Things like Karmada are huge platforms sweeping in scope/goals. Having to adopt something like that for this purpose is wildly heavy handed.

The Application CRD does the following:

  1. Provide a metadata object you can add arbitrary data to that is deployed with your stack
  2. Capture all the k8s resources encompassing a single "application" and group them into a single object that can be the source of truth for describing all the resources the app owns/uses
borgilb commented 2 years ago

The thing that makes the Application CRD nice is how simple and focused in scope it is. You can use it with any deployment approach and tooling.

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 1 year ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/application/issues/223#issuecomment-1397295968): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.