GlobalNet: explicitly document that Global Ingress IP CR creation by users is forbidden.

[yboaron]

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'

[stale]

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.

[stale]

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.

[dfarrell07]

There are a number of CRDs that might parallel this (should not be edited by users), like ServiceImport, Cluster, Endpoint, Gateway.

[stale]

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.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further
activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further
activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further
activity occurs. Thank you for your contributions.