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

Fed canary upgrades: status should be forwards and backwards compatible #7238

Open
jenshu opened this issue Sep 26, 2022 · 1 comment
Open
Assignees
Labels
Area: Gloo Fed Issues related to the Gloo Fed project in solo-projects Size: M 3 - 5 days stale Issues that are stale. These will not be prioritized without further engagement on the issue. Type: Enhancement New feature or request
Milestone

Comments

@jenshu
Copy link
Contributor

jenshu commented Sep 26, 2022

Version

No response

Is your feature request related to a problem? Please describe.

After making the federated resource namespaced status change, make sure status marshalling/unmarshalling doesn't error in Gloo Fed. Both the old and new Gloo Fed instance should be able to read from and write to the status successfully.

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional Context

No response

@jenshu jenshu added the Type: Enhancement New feature or request label Sep 26, 2022
@jenshu jenshu added Size: S 1 - 3 days Size: M 3 - 5 days and removed Size: S 1 - 3 days labels Sep 26, 2022
@jenshu jenshu added this to the Fed canary milestone Oct 11, 2022
@sam-heilbron sam-heilbron self-assigned this Oct 19, 2022
@jenshu jenshu added Area: Gloo Fed Issues related to the Gloo Fed project in solo-projects and removed Area: Fed labels Mar 21, 2023
Copy link

github-actions bot commented Jun 5, 2024

This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs.

@github-actions github-actions bot added the stale Issues that are stale. These will not be prioritized without further engagement on the issue. label Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Gloo Fed Issues related to the Gloo Fed project in solo-projects Size: M 3 - 5 days stale Issues that are stale. These will not be prioritized without further engagement on the issue. Type: Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants