Project Status? about application HOT 9 CLOSED

I get the impression that this effort is being driven by Google exclusively: https://cloud.google.com/kubernetes-applications

Are they just not trying super hard to court the wider open source community or does no one else give a crap about it?

There is actually a dashboard item in the GKE console for "Kubernetes Applications". I think this is just a GCP specific feature mostly for 3rd parties to support easy install of their apps onto GKE clusters.

from application.

KubeVela, which is also a CNCF-incubated project, seems like a promising alternative. It implements the Open Application Model (OAM) standard, which also offers an Application CRD.

It promises to be flexible and customizable through its use of Cue.

from application.

I make extensive use of Argo CD and only just noticed this repo. I am wondering if the ground work done here might help standardize what the various kind: Application resouces have across various apiVerson specific definitions.

from application.

Yes, Google has historically driven the Application CRD work. Google's general focus is to support complementary technologies that can be composed with existing solutions in the ecosystem. The primary focus of the App CRD is Status / and metadata (which Google exposes in the GKE UI), in case our customers would like a deeper integration with the GKE UI for their app teams.

@kow3ns might have some thoughts as well given that he's the original author of it.

from application.

Should open any issues/questions I have with GCP support instead of here? I get the impression these github issues aren't going to be front and center for them.

from application.

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:

• 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:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

from application.

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:

• 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:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

from application.

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:

• 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 or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close

from application.

@k8s-triage-robot: Closing this issue.

from application.