Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[KF 1.0 Compliance] app.kubernetes.io labels on every resource #3755

Closed
Bobgy opened this issue May 13, 2020 · 6 comments
Closed

[KF 1.0 Compliance] app.kubernetes.io labels on every resource #3755

Bobgy opened this issue May 13, 2020 · 6 comments
Assignees
Labels
deployment lifecycle/frozen priority/p2 status/triaged Whether the issue has been explicitly triaged

Comments

@Bobgy
Copy link
Contributor

Bobgy commented May 13, 2020

Part of #2884
Compliance doc: https://github.com/kubeflow/community/blob/master/guidelines/application_requirements.md

Description Category Explanation
app.kubernetes.io labels on every resource Required Every resource that is part of the application should include the labels recommended by Kubernetes, currently:app.kubernetes.io/nameapp.kubernetes.io/instanceapp.kubernetes.io/versionapp.kubernetes.io/componentapp.kubernetes.io/part-ofapp.kubernetes.io/managed-bySee example here
@Bobgy
Copy link
Contributor Author

Bobgy commented May 13, 2020

The problem is that common labels feature in kustomize cannot be used for applying these labels: kubeflow/manifests#1131

Because it is applied to selectors too, while selectors have to be immutable for upgrade.

Due to the limitations, I think it's better to defer this requirement to post 1.0 until there's a maintainable solution.

Upstream kustomize has a solution to add labels commonly without changing selector: kubernetes-sigs/kustomize#1009 (comment)

but I tried, the feature wasn't even introduced in kustomize 3.1.0, it will take a long time before kubectl kustomize picks it up.

@Bobgy Bobgy self-assigned this May 13, 2020
@Bobgy Bobgy added priority/p2 deployment status/triaged Whether the issue has been explicitly triaged labels May 13, 2020
@Bobgy
Copy link
Contributor Author

Bobgy commented May 13, 2020

/cc @jlewi
Sounds reasonable to defer this until later than KFP 1.0?

@stale
Copy link

stale bot commented Aug 11, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the lifecycle/stale The issue / pull request is stale, any activities remove this label. label Aug 11, 2020
@Bobgy
Copy link
Contributor Author

Bobgy commented Aug 12, 2020

/lifecycle frozen

@rimolive
Copy link
Member

Closing this issue. Looks like the resources are already annotated.

/close

Copy link

@rimolive: Closing this issue.

In response to this:

Closing this issue. Looks like the resources are already annotated.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deployment lifecycle/frozen priority/p2 status/triaged Whether the issue has been explicitly triaged
Projects
None yet
Development

No branches or pull requests

3 participants