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

Explore exposing information from the Kuma API in Kubernetes Events and status #3734

Open
michaelbeaumont opened this issue Jan 20, 2022 · 11 comments
Open

Explore exposing information from the Kuma API in Kubernetes Events and status #3734

michaelbeaumont opened this issue Jan 20, 2022 · 11 comments
Labels
area/api area/k8s kind/design Design doc or related triage/accepted The issue was reviewed and is complete enough to start working on it
Milestone
2.10.x

Comments

@michaelbeaumont
Copy link
Contributor

michaelbeaumont commented Jan 20, 2022 •
edited by lahabana
Loading

Description

Kubernetes offers the resource status convention for exposing information about the current state of resources in the Kubernetes API. We should explore what information about Kuma resources or from the Kuma API we can surface on the Kuma CRDs. (e.g. applied policies)

Goal:

  • Build a MADR with events that could be added
  • Figure out if we ever need events on universal
@michaelbeaumont michaelbeaumont added area/k8s area/api triage/pending This issue will be looked at on the next triage meeting kind/design Design doc or related labels Jan 20, 2022
@lahabana lahabana 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 Jan 24, 2022
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Mar 17, 2022
@github-actions
Copy link
Contributor

This issue was inactive for 30 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 promptly or attend the next triage meeting.

@lahabana lahabana removed the triage/stale Inactive for some time. It will be triaged again label Jul 11, 2022
@jakubdyszkiewicz
Copy link
Contributor

Triage: an equivalent in universal would be required here. We can also implement this way "warnings" about the state of the mesh.

@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 21, 2022
@michaelbeaumont
Copy link
Contributor Author

@lahabana @jakubdyszkiewicz could we implement this only for k8s at first? Like the postgres store just has a noop on UpdateStatus?

@michaelbeaumont michaelbeaumont removed the triage/stale Inactive for some time. It will be triaged again label Nov 21, 2022
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Feb 20, 2023
@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.

@michaelbeaumont michaelbeaumont removed the triage/stale Inactive for some time. It will be triaged again label Feb 20, 2023
@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 May 22, 2023
@slonka slonka removed the triage/stale Inactive for some time. It will be triaged again label May 30, 2023
@slonka
Copy link
Contributor

slonka commented May 30, 2023

re-pinging @lahabana @jakubdyszkiewicz: could we implement this only for k8s at first? Like the postgres store just has a noop on UpdateStatus?

@michaelbeaumont
Copy link
Contributor Author

👍 on that, we can add events the same way.

@lahabana
Copy link
Contributor

If it's in k8s does this replace insights?

@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 Aug 30, 2023
@lahabana lahabana removed the triage/stale Inactive for some time. It will be triaged again label Sep 5, 2023
@michaelbeaumont michaelbeaumont mentioned this issue Nov 9, 2023
Closed
@michaelbeaumont michaelbeaumont changed the title Explore exposing information from the Kuma API in Kubernetes CRD status Explore exposing information from the Kuma API in Kubernetes Events and status Nov 9, 2023
@lahabana lahabana mentioned this issue Nov 13, 2023
Closed
@michaelbeaumont michaelbeaumont mentioned this issue Nov 21, 2023
Closed
@lahabana lahabana added this to the 2.7.x milestone Jan 10, 2024
@lahabana lahabana modified the milestones: 2.7.x, 2.8.x Mar 26, 2024
@lahabana lahabana modified the milestones: 2.8.x, 2.9.x Apr 24, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Jul 24, 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.

@lahabana lahabana modified the milestones: 2.9.x, 2.10.x Jul 24, 2024
@michaelbeaumont michaelbeaumont mentioned this issue Jul 24, 2024
Open
@lobkovilya lobkovilya removed the triage/stale Inactive for some time. It will be triaged again label Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/api area/k8s kind/design Design doc or related triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Milestone
2.10.x
Development

No branches or pull requests
5 participants
@lahabana @michaelbeaumont @slonka @jakubdyszkiewicz @lobkovilya