Feature/import config file #194
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
schnatterer
force-pushed
the
feature/import_config_file
branch
from
6d84eab
to
0bbb901
Compare
We don't want to write our own validator. I think it's muss less complex to solve this problem using configuration of the SchemaGenerator.
…config.yaml for ingress-nginx controller
This will make it easier to use in the future without having to cast it
schnatterer
force-pushed
the
feature/import_config_file
branch
from
0bbb901
to
6685d37
Compare
|
I tested this successfully with this config # $schema: docs/configuration.schema.json
features:
ingressNginx:
active: true
helm:
values:
controller:
replicaCount: 4
#extraArgs:
# default-ssl-certificate: "ingress-nginx/wildcard-cert"
service:
externalTrafficPolicy: Local
internal:
enabled: true
annotations:
service.beta.kubernetes.io/azure-load-balancer-internal: "true"
service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path: "/healthz" docker run --rm -t -u $(id -u) \
-v ~/.config/k3d/kubeconfig-gitops-playground.yaml:/home/.kube/config \
-v $(pwd)/gitops-playground.yaml:/config/gitops-playground.yaml \
--net=host \
gitops-playground:dev -x --yes --argocd --ingress-nginx --base-url=http://localhost --config-file=/config/gitops-playground.yamlBTW, setting the wildcard cert commented above can be tested like so openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout tls.key -out tls.crt -subj "/CN=localhost"
kubectl create secret tls wildcard-cert --cert=tls.crt --key=tls.key -n ingress-nginx |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.