Is Vertical Pod Autoscaling supported on Azure Kubernetes Service? I am unable to find any links or page on msdn with the details about it.
The Vertical Autoscaler is not supported in AKS, as the feature is still in Alpha in the upstream Kubernetes project. As the features matures in upstream it will be integrated into the service.
Related
We are about to apply SCDF along with K8s but not sure whether we should deploy
all (or partially) the components (SCDF, DB, broker) on k8s cluster or we can use all the 3 components separately and just use k8s to deploy the data pipelines only.
thanks
I have a basic question about deploying Spring tasks/batch jobs on SCDF Kubernetes. Now if I deploy the SCDF on Kubernetes and then schedule a batch job, which Kubernetes cluster is the batch job deployed on? where is the pod created? the same cluster where the SCDF server is running?
By default the apps are deployed on the same cluster and namespace as the SCDF server but this is configurable. You can configure any number of target “platforms”. Each platform is essentially a set of deployment properties keyed to a logical name. You can set the platform name as a parameter on which each task is launched. This is described here
I am trying to implement dynamic slave provisioning on Jenkins by using Kubernetes Plugin. My Jenkins master is running on on-premise machine whereas the Kubernetes cluster is on Google cloud(GKE). After initial configuration as per plugin documentation I was able to see the agent PODS on GKE Cluster but not in running state. PODS are getting exited as they are not able to reach the Jenkins URL (which is on-premises). Has any one tried implementing such scenario? If yes then help would be much appreciated. I am not getting any clue how to get this implemented.
If it is not feasible then I have to look for GCE plugin which will provision VM's as agents.
Thanks in advance..
I have a .NET core web API and Angular 7 app that I need to deploy to multiple client servers, potentially running a plethora of different OS setups.
Dockerising the whole app seems like the best way to handle this, so I can ensure that it all works wherever it goes.
My question is on my understanding of Kubernetes and the distribution of the application. We use Azure Dev Ops for build pipelines, so if I'm correct would it work as follows:
1) Azure Dev Ops builds and deploys the image as a Docker container.
2) Kubernetes could realise there is a new version of the docker image and push this around all of the different client servers?
3) Client specific app settings could be handled by Kubernetes secrets.
Is that a reasonable setup? Have I missed anything? And are there any recommendations on setup/guides I can follow to get started.
Thanks in advance, James
Azure DevOps will perform the CI part of your pipeline. Once it is completed, Azure DevOps will push images to ACR. CD part should be done either directly from Azure DevOps (You may have to install a private agent on your on-prem servers & configure firewall etc) or Kubernetes native CD tools such as Spinnaker or Jenkins-X. Secrets should be kept in Kubernetes secrets.
I have worked with Jenkins X which is Jenkins running in Kubernetes cluster and I am seeing a new feature in the Google Cloud marketplace here, which is offering Jenkins, are these same?
The Jenkins currently available in Google Cloud Marketplace is for the Jenkins Server.
Jenkins X is a new project, that is utilizing Kubernetes and ecosystem to provider a Kubernetes native equivalent to the Jenkins server, and provide horizontal scaling with no single point of failure and small footprint.