Make Ambassador "Kubernetes-Native" with Custom Resource Definitions (CRD)
See original GitHub issueI wish I could just kubectl get mappings
.
Are you all planning to use CRDs (or even an aggregated API)? https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/
Issue Analytics
- State:
- Created 5 years ago
- Reactions:8
- Comments:11 (10 by maintainers)
Top Results From Across the Web
Make Ambassador "Kubernetes-Native" with Custom ... - GitHub
Make Ambassador "Kubernetes-Native" with Custom Resource Definitions ... a) Create CRD yaml files, include them in the helm chart. extend ...
Read more >Extend the Kubernetes API with CustomResourceDefinitions
This page shows how to install a custom resource into the Kubernetes API by creating a CustomResourceDefinition. Before you begin You need ...
Read more >Kubernetes Operators and CRDs with Ambassador: Admiralty ...
Adrien Trouillaud has recently published an article on the Admiralty blog about his experience of creating a Kubernetes Custom Resource ...
Read more >Creating Custom Kubernetes Operators - Weaveworks
The Custom Resource Definition (CRD) · A configmap parameter: a string that specifies the name of the ConfigMap resource. · A podSelector ...
Read more >ambassador 6.2.1 · helm/datawire - Artifact Hub
kubectl create namespace ambassador $ helm install my-release ... Ambassador is configured using Kubernetes Custom Resource Definitions (CRDs).
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes, this is something we’d like to do. (Ambassador was originally written after TPRs were deprecated and before CRDs existed.) It’s a little ways off, though, as we’re migrating to Envoy’s ADS and v2 config YAML first.
Done in 0.70.0.