Understanding Kubernetes Canary Deployment With Architecture Diagram Part-II

Comments

Post a Comment

Popular posts from this blog

[Solved] Gitlab remote: ERROR: Your SSH key has expired.

  Error:- We have been using Gitlab and recently I got the following error while pushing my change to the Gitlab Repository remote: remote: ======================================================================== remote: remote: ERROR: Your SSH key has expired. remote: remote: ======================================================================== remote: fatal: Could not read from remote repository. Cause:- The reason for this failure was that i created a ssh key about a year ago and gitlab by default puts a security policy that your ssh key will get expire after 1 year. This is something built in to improve security in Gitlab now because that timeperiod has elapsed of 1 year thats why it gives that error of ssh key has expired.
Read more

[Resolved] groupVersion shouldn't be empty

  Issue:-  When creating the simple resource like pod, replicaset, deployments etc got a groupVersion error specified below.  Error:-   groupVersion shouldn't be empty Effect:- Not able to create the resource because of the above error apiversion: v1 kind: Pod metadata: name: pod2 spec: containers: - name: c1 image: nginx Resolution:- If you look at the above configuration precisely you will find the  apiversion   has been specified incorrectly. It should have been  apiVersion   k.So just a difference of block letter can make that error. The same error will occur even if you forgot to mention the apiVersion in the configuration or it is misspelled. Below configuration will work fine. apiVersion: v1 kind: Pod metadata: name: pod2 spec: containers: - name: c1 image: nginx   Explanation:- apiVersion is hardcoded in the kubernetes. So if you misspell it, not use it or make a e...
Read more

[Solved] Error: Package: jenkins-2.303.1-1.1.noarch (jenkins) Requires: daemonize --skip-broken to work

Issue:-   The issue occurs when trying to install the jenkins on the Centos7 EC2 Instance in the AWS. # yum install jenkins -y Error:-  --> Finished Dependency Resolution Error: Package: jenkins-2.303.1-1.1.noarch (jenkins) Requires: daemonize You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Cause:- Basically daemonize runs a command as a Daemon in the Centos. Since the package is missing in the version of the Centos you running thats why this error is coming. Think of it like a dependency which is required by the Jenkins to run but since you missing on the Daemonize thats why its giving the error. Resolution:- Daemonize doesn't ship in the default repository thats why yum is not able to resolve it. You will need to install the Daemonize from the Epel repository which is the extra package for enterprise linux as # yum install epel-release -y # yum install daemonize -y Than you can...
Read more