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

dataPlaneOptions ingress type: ClusterIP does not produce a valid service definition for the dataplane. #811

Closed
scottaubrey opened this issue Oct 28, 2024 · 1 comment · Fixed by #812
Assignees
Labels
bug Something isn't working
Milestone

Comments

@scottaubrey
Copy link

scottaubrey commented Oct 28, 2024

Current Behavior

Setting a data plane ingress type to type: ClusterIP should be possible, but fails to deploy. The controller manager produces an error similar to :

"Service \"dataplane-ingress-epp-server-gateway-xj9d2-57ckv\" is invalid: spec.externalTrafficPolicy: Invalid value: \"Cluster\": may only be set for externally-accessible services"

Expected Behavior

Deployed gateway serving internal cluster traffic only.

Steps To Reproduce

Specify the service type on a GatewayConfiguration object:

spec:
  dataPlaneOptions:
    network:
      services:
        ingress:
          externalTrafficPolicy: null
          type: ClusterIP # internal gateway only

This seems to be caused by the changes made here, and in particular the defaulting to Cluster type done here. Setting spec.dataPlaneOptions.network.services.ingress.externalTrafficPolicy to any valid value does not produce a valid gateway service definition while type is ClusterIP.

Operator Version

1.3

kubectl version

kubectl version
Client Version: v1.31.0
Kustomize Version: v5.4.2
Server Version: v1.30.4-eks-a737599

@scottaubrey scottaubrey added the bug Something isn't working label Oct 28, 2024
@pmalek
Copy link
Member

pmalek commented Oct 28, 2024

@scottaubrey thanks for reporting this.

#812 should fix this.

@pmalek pmalek self-assigned this Oct 28, 2024
@pmalek pmalek added this to the KGO v1.4.x milestone Oct 28, 2024
@pmalek pmalek linked a pull request Oct 28, 2024 that will close this issue
1 task
@pmalek pmalek closed this as completed Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants