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

Improve Gateway API concerning protocol: HTTPS #7132

Closed
2 tasks done
jeromeguillaume opened this issue Mar 25, 2024 · 0 comments · Fixed by #7182
Closed
2 tasks done

Improve Gateway API concerning protocol: HTTPS #7132

jeromeguillaume opened this issue Mar 25, 2024 · 0 comments · Fixed by #7182

Comments

@jeromeguillaume
Copy link

Where is the problem?

https://docs.konghq.com/kubernetes-ingress-controller/latest/concepts/gateway-api/#gateway-management

What happened?

About the protocol: HTTPS property in the example, it lacks the tls and hostname properties. I guess it also concerns the protocol: TLS

  1. If we don't put the tls property, there is an error message in the console when we do kubectl apply: Invalid value: "array": tls must be specified for protocols ['HTTPS', 'TLS']
    2.If don't put the hostname property, there is an error message in the Ingress Controller pod: ["must be a valid hostname with a wildcard prefix '*' ornwithout"],"type":"ERROR_TYPE_FIELD"}])

What did you expect to happen?

Having a HTTPS and TLS proper example like this:

  1. Create a kong-secret-proxy with kubectl create secret tls
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: kong
  namespace: kong
spec:
  gatewayClassName: kong
  listeners:
  - name: proxy-kong
    port: 80
    protocol: HTTP
  - name: proxy-kong-tls
    port: 443
    protocol: HTTPS
    hostname: kong.client.com
    tls:
      mode: Terminate
      certificateRefs:
        - kind: Secret
          group: 
          name: kong-secret-proxy
    allowedRoutes:
      namespaces:
        from: All

Code of Conduct and Community Expectations

  • I agree to follow this project's Code of Conduct
  • I agree to abide by the Community Expectations
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 a pull request may close this issue.

1 participant