Add CRD Controller to Mesh Controller #12
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
|
This PR also extends the kubectl client logic to automatically pull from: -> kubeconfig |
|
CRD registration will be via the helm chart, and will not require creation via code at this time. |
change vscode gitignore go mod vendor add informer controller fix commit fix mod
|
In simply kube client creation. If you want to use an external cluster config you have to use this command for xample ./dist/i3o --master https://localhost:6443 --kubeconfig=/tmp/k3s-output/kubeconfig.yaml --debugFor an in cluster config this command ./dist/i3o --debug |
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.
This PR allows for the monitoring of IngressRoute objects using the traefik API, and allowing for CRD compatible clients for CRUD operations.