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

add default annotations and possibility to use same ingress for http-… #2106

Open
wants to merge 7 commits into
base: v2.x
Choose a base branch
from

Conversation

chris8205
Copy link
Contributor

  • possible to use the http-service ingress for http-service and mqtt-websocket-service
    mqtt is listening on /mqtt
    while FROST-Server is listening default on /FROST-Server

  • enhancement for mqtt and http-service annotations

annotations: {{- include "common.tplvalues.render" ( dict "value" $annotations "context" $) | nindent 4 }}
{{- /*Following annotation can't be described in the _helpers.tpl, so actually it hast to stay here*/ -}}
{{- if and .Values.frost.mqtt.ingress.useSameAsHttp (or (eq .Values.frost.http.ingress.ingressProvider "kubernetes-nginx") (not .Values.frost.http.ingress.ingressProvider))}}
nginx.ingress.kubernetes.io/server-snippets: |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

According to the docs that should be without s: server-snippet. Are you sure this works?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

@@ -126,11 +126,11 @@ frost:
nodePort:
servicePort: 80
ingress:
enabled: true
enabled: false
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

HTTP-ingress disabled by default? That seems odd?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

# className: nginx-hamel
## Defines the type of ingress-Controller in use (nginx [default], agic )
# ingressProvider: agic
ingressClassName: regioit-private-ingress
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That looks like an internal test name, is that OK, or should it be "anonymised"?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove values for test purposes

Comment on lines 164 to 165
serviceHost: frost.hameltest.intern.cnaphci.regioit.cloud
urlSubPath: "meinFrost"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That looks like an internal test name, is that OK, or should it be "anonymised"?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove values for test purposes

enabled: false
secretName: []
enabled: true
secretName: hamel-test-frost-server-http-tls
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That looks like an internal test name, is that OK, or should it be "anonymised"?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove values for test purposes

# className: azure-application-gateway
## Defines the type of ingress-Controller in use (nginx [default], agic or traefik)
# ingressProvider: agic
ingressClassName: regioit-private-ingress
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That looks like an internal test name, is that OK, or should it be "anonymised"?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove values for test purposes


# FROST-Server MQTT business settings
serviceHost: "" # default URI is the same then frost.http.serviceHost"
serviceHost: "mqtt.hameltest.intern.cnaphci.regioit.cloud" # default URI is the same then frost.http.serviceHost"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That looks like an internal test name, is that OK, or should it be "anonymised"?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove values for test purposes

enabled: false
secretName: []
enabled: true
secretName: hamel-test-frost-server-mqtt-tls
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That looks like an internal test name, is that OK, or should it be "anonymised"?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove values for test purposes

revoke test values
@chris8205
Copy link
Contributor Author

remove values for test purposes

uncomment tls values
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 this pull request may close these issues.

3 participants