istio-initializer | Kubernetes Initializer that injects the Istio sidecar | Service Mesh library
kandi X-RAY | istio-initializer Summary
kandi X-RAY | istio-initializer Summary
Kubernetes Initializer that injects the Istio sidecar into pods.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- main is the main entry point for kubeconfig
- configmapToConfig converts a ConfigMap .
- initializePod is used to update the initializer
istio-initializer Key Features
istio-initializer Examples and Code Snippets
Community Discussions
Trending Discussions on istio-initializer
QUESTION
I'm trying to install Istio with automatic sidecar injection into Kubernetes. My environment consists of three masters and two nodes and was built on Azure using the Azure Container Service marketplace product.
Following the documentation located here, I have so far enabled RBAC
and DynamicAdmissionControl
. I have accomplished this by modifying /etc/kubernetes/istio-inializer.yaml
on the Kubernetes Master by adding the following content outlined in red and then restarting the Kubernetes Master using the Unix command, reboot
.
The next step in the documentation is to apply the yaml using kubectl
. I assume that the documentation intends for the user to clone the Istio repository and cd
into it before this step but that is unmentioned.
ANSWER
Answered 2017-Sep-28 at 17:15Seems to be a versioning problem as the alpha feature is supported for k8s version> 1.7 as mentioned here (https://kubernetes.io/docs/admin/extensible-admission-controllers/#what-are-initializers).
1.7 introduces two alpha features, Initializers and External Admission
Webhooks, that address these limitations. These features allow admission controllers to be developed out-of-tree and configured at runtime.
And it is possible to deploy a version of kubernetes >= 1.7.4 to Azure. Note sure about the deployed version using the portal. But if you use acs-egnine to generate the ARM template, it is possible to deploy a cluster with version 1.7.5.
You can refer here for the procedures https://github.com/Azure/acs-engine. Basically it involves three steps. First, you should create the json file by referring to the clusterDefinition section. To use version 1.7.5, you should specify the attribute "orchestratorRelaease" to be "1.7" and also enable the RBAC by specifying the attribute "enableRbac" to be true. Second, use the acs engine (version >= 0.6.0) to parse the json file to ARM template (azuredeploy.json & azuredeploy.parameters.json should be created). Lastly, use the command "New-AzureRmResourceGroupDeployment" in powershell to deploy the cluster to Azure.
Hope this helps :)
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install istio-initializer
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page