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

Kubernetes service annotations should be exposed like all other resources #5019

Closed
mcasperson opened this issue Oct 23, 2018 · 2 comments

Comments

@mcasperson
Copy link

commented Oct 23, 2018

Platforms like Ambassador make heavy use of service annotations, so these fields should be exposed for service resources like they are for ingress and deployment resources.

@mcasperson mcasperson added this to the 2018.9.0 milestone Oct 23, 2018
@mcasperson mcasperson self-assigned this Oct 23, 2018
@mcasperson mcasperson closed this Oct 23, 2018
@octoreleasebot

This comment has been minimized.

Copy link

commented Oct 23, 2018

Release Note: K8S service annotations now exposed like Ingress and Deployment annotations

@lock

This comment has been minimized.

Copy link

commented Jan 21, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants
You can’t perform that action at this time.