-
Notifications
You must be signed in to change notification settings - Fork 51
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
GlobalNet: explicitly document that Global Ingress IP CR creation by users is forbidden. #710
Comments
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions. |
There are a number of CRDs that might parallel this (should not be edited by users), like ServiceImport, Cluster, Endpoint, Gateway. |
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
Though Global Ingress IP CRs should be created only by GN controller to assign addresses for exported services, it is still possible for user to create such a resource.
Applying the resource below by the user will end up with an incorrect ingress IP allocation.
'apiVersion: submariner.io/v1
kind: GlobalIngressIP
metadata:
name: fufu
namespace: default
spec:
podRef:
name: fufu
target: kuku'
The text was updated successfully, but these errors were encountered: