kubernetes-deploy | Continuous Deployment library

1. By following the above tutorial if you cannot access the management console as https://wso2is/carbon/admin/login.jsp. Then there should be a issue in your load balancing. use

kubectl get ing -n wso2

Command to get the ingress it should be exposed with the port 443 and there should be minikube ip in the ip address column. If this does not seems right use

kubectl describe ing wso2is-ingress -n wso2

And

kubectl logs -n kube-system

For debugging.

1. jks files need to be provided as secrets not as config maps. You can refer this blog to get some idea https://www.padok.fr/en/blog/kubernetes-secrets

You created ConfigMap and trying to get value from secret. If you want set value from configmap then update env like following

From the docs

1. Establish an authentication mechanism between AKS and ACR

2. Ensure you have the proper AKS credentials using az aks get-credentials -g myResourceGroup -n myAKSCluster

3. Apply the kubernetes deployment yaml to AKS

The new DB schema can be create on the running Pod:

1. Find out the name of your Postges Pod: kubectl get po
2. Log into your Pod: kubectl exec -it [Name-of-Pod] -- sh
3. Copy your schema dump file to the Pod: kubectl cp [Name-of-File] [Name-of-Pod]:[Name-of-File]
4. Install schema with psql tool: psql -U username dbname < [Name-of-File]

The issue is here: error while creating mount source path '/mnt/data': mkdir /mnt/data: read-only file system.

You need to make sure postgres-pv-claim is writable. You need to recreate the pv and pv claim with RWO access (you must have mistyped it to RO instead which is why you ran into the issue) then try to deploy postgres pod which should fix the issue.

Provisioning persistent volume in GKE you don't need to create PersistentVolume objects they are dynamically created by GKE. So solve the Warning FailedScheduling 69s (x10 over 7m35s) issue

1. remove storageClassName property from your pvc and
2. delete pv

which should fix the issue. Please see below revised postgres-storage.yaml.

The snippets you provide are regrettably insufficient but you have the basics.

I had a Google for you for a tutorial and -- unfortunately -- nothing obvious jumped out. That doesn't mean that there isn't one, just that I didn't find it.

You've got the right idea and there are quite a few levels of technology to understand but, I commend your approach and think we can get you there.

1. Let's start with a helloworld Node.JS tutorial

https://nodejs.org/en/docs/guides/getting-started-guide/

1. Then you want to containerize this

https://nodejs.org/de/docs/guides/nodejs-docker-webapp/

For #3 below, the last step here is:

So from the Kubernetes deployment documentation, one use case is:

Declare the new state of the Pods by updating the PodTemplateSpec of the Deployment. A new ReplicaSet is created and the Deployment manages moving the Pods from the old ReplicaSet to the new one at a controlled rate. Each new ReplicaSet updates the revision of the Deployment.

So knowing the deploying is not relevant unless you want to rollback. So what you need is to get the pods to see each other. In that case, you need a headless service.

https://dev.to/kaoskater08/building-a-headless-service-in-kubernetes-3bk8

There you can get the pod DNS and tag them in your Redis by IP or DNS

EDIT:

For getting the deployment, every pod has an env var called HOSTNAME, for example (in my environment):

can you check permissions on /etc/rabbitmq/. does the user has permission to copy the file to above location?

For stateful sets you can implement Blue/Green update, Rolling update, OnDelete strategy.

Stateful sets used when you are running stateful application inside pod. For example storing something in RAM. redis database run as stateful sets.

Stateful sets managed the sequence automatically like example 'redis-0','redis-1' so if anything goes wrong to pod it will close the process and start new process and try to manage the same state.

If you use strategy Recreate it will delete pod first terminate it and again start the new one it's for stateless applications. Also same way works for Rolling update.