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

group gateway.gloo.solo.io -> gateway.kgateway.dev #10544

Merged
merged 3 commits into from
Jan 29, 2025
Merged

Conversation

yuval-k
Copy link
Contributor

@yuval-k yuval-k commented Jan 29, 2025

change the group of our CRDs
also added basic yaml tests for upstream and route options to prove out the change

@yuval-k yuval-k enabled auto-merge January 29, 2025 15:14
@@ -7,9 +7,9 @@ metadata:
labels:
app: gloo-gateway
app.kubernetes.io/name: gloo-gateway
name: directresponses.gateway.gloo.solo.io
name: directresponses.gateway.kgateway.dev
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

general question - do we still need the gateway or can we just shorten it to directresponses.kgateway.dev?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good question - I did that as looking at other projects (like istio) it seems common to have x. format where X is a "theme" (security,traffic, etc..). that's said, there's a chance that given our scope our only "theme" will be gateway. so not sure

@yuval-k yuval-k added this pull request to the merge queue Jan 29, 2025
Merged via the queue into main with commit 2a4ff05 Jan 29, 2025
8 checks passed
@yuval-k yuval-k deleted the yuval-k/change-group branch January 29, 2025 16:23
@lgadban lgadban linked an issue Jan 30, 2025 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

rename API group for CRDs
2 participants