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.

Sign up for GitHub

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

Jump to bottom

Better way of syncing annotations to docs #1523

Open
slonka opened this issue Nov 13, 2023 · 5 comments
Open

Better way of syncing annotations to docs #1523

slonka opened this issue Nov 13, 2023 · 5 comments
Labels
kind/improvement Improvement on an existing feature triage/accepted The issue was reviewed and is complete enough to start working on it

Comments

@slonka
Copy link
Contributor

slonka commented Nov 13, 2023

Description

During review of kumahq/kuma#8319 I noticed with Ilya that https://kuma.io/docs/2.4.x/reference/kubernetes-annotations/#kubernetes-annotations-and-labels is missing kuma.io/sidecar-uid annotation. We might be missing some others. I guess we could have some automated way of syncing them.
@slonka slonka added triage/pending This issue will be looked at on the next triage meeting kind/improvement Improvement on an existing feature labels Nov 13, 2023
@jakubdyszkiewicz jakubdyszkiewicz added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Nov 13, 2023
@jakubdyszkiewicz
Copy link
Contributor

Triage: there should be a mechanism in Kuma to generate YAML file with all annotations that we then sync to docs.

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Feb 12, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@slonka slonka removed the triage/stale Inactive for some time. It will be triaged again label Feb 12, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label May 13, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@jakubdyszkiewicz jakubdyszkiewicz removed the triage/stale Inactive for some time. It will be triaged again label May 13, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Aug 12, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@slonka slonka removed the triage/stale Inactive for some time. It will be triaged again label Aug 12, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Nov 11, 2024
@lukidzi lukidzi removed the triage/stale Inactive for some time. It will be triaged again label Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/improvement Improvement on an existing feature triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@slonka @jakubdyszkiewicz @lukidzi