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

Dekorate picks a random port for Route when having multiple container ports #1124

Closed
Sgitario opened this issue Jan 12, 2023 · 0 comments · Fixed by #1126
Closed

Dekorate picks a random port for Route when having multiple container ports #1124

Sgitario opened this issue Jan 12, 2023 · 0 comments · Fixed by #1126

Comments

@Sgitario
Copy link
Collaborator

When having:

---
apiVersion: v1
kind: Service
metadata:
  name: app
spec:
  ports:
    - name: https
      port: 443
      protocol: TCP
      targetPort: 8443
    - name: http
      port: 80
      protocol: TCP
      targetPort: 8080
  type: ClusterIP

When building the manifests, the generated Route in OpenShift sometimes picks HTTP and some othertimes uses HTTPS.

Sgitario added a commit to Sgitario/dekorate that referenced this issue Jan 12, 2023
And avoid using the problematic `getHttpPort(config)`.
Fix dekorateio#1124
Sgitario added a commit to Sgitario/dekorate that referenced this issue Jan 12, 2023
And avoid using the problematic `getHttpPort(config)`.
Fix dekorateio#1124
Sgitario added a commit that referenced this issue Jan 12, 2023
And avoid using the problematic `getHttpPort(config)`.
Fix #1124
Sgitario added a commit to Sgitario/dekorate that referenced this issue Jan 12, 2023
And avoid using the problematic `getHttpPort(config)`.
Fix dekorateio#1124
Sgitario added a commit to Sgitario/dekorate that referenced this issue Jan 12, 2023
And avoid using the problematic `getHttpPort(config)`.
Fix dekorateio#1124
Sgitario added a commit to Sgitario/dekorate that referenced this issue Jan 12, 2023
And avoid using the problematic `getHttpPort(config)`.
Fix dekorateio#1124
Sgitario added a commit that referenced this issue Jan 13, 2023
And avoid using the problematic `getHttpPort(config)`.
Fix #1124
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