Cloud Devops Automation

  Issue:-  Terraform run time error on apply that the parameter Header Cloudfront-Viewer-Address is not allowed Error:-     error updating CloudFront Distribution: InvalidArgument: The parameter Header Name contains Cloudfront-Viewer-Address that is not allowed. Effect:- SCloudfront-Viewer-Address contains the IP Address of the viewer that sent the request to Cloudfront, and the port used for the request. For e.g 3.110.159.137:443. Because the header is not whitelisted the same value is not available in the system. Resolution:- Change the configuration under the Behaviours in the cloudfront from  Legacy cache settings to   Legacy cache settings to Cache policy and origin request policy (recommended) Explanation:- The header  cloudfront-viewer-address is supported by the Legacy cache settings to Cache policy and origin request policy (recommended) only and you cannot use it with the   Legacy cache settings as per the AWS Documentation.

 The solution for the above problem has been discussed in the link below https://www.unixcloudfusion.in/2022/02/solved-caliconode-is-not-ready-bird-is.html

  Issue:-  The Issue was first recognised after we expose a service using the Nodeport and tried to access over the localhost on other node followed by Nodeport number. But the curl request failed with timeout On Inspecting the containers of the master node one of the containers of the calico node was not ready. When I used the describe container for that service it gave the error mentioned below. Error:-    Normal   Created    14m                kubelet            Created container calico-node   Normal   Started    14m                kubelet            Started container calico-node   Warning  Unhealthy  14m (x3 over 14m)  kubelet            Readiness probe failed: calico/node is not ready: BIRD is not ready: Error querying BIRD: unable...

  Issue:-  So received the error while deploying the visualizer , specifically for putting the constraint node.role=manager. Error:-  [root@managernode ~]# docker service create --name=viz --publish=8080:8080/tcp --constraint==node.role=manager --mount type=bind,src=/var/run/docker.sock,dst=/var/run/docker.sock dockersamples/visualizer Error response from daemon: rpc error: code = Unknown desc = constraint expected one operator from ==, != Resolution:- You need to use the == beween the node.role==manager in order to solve the problem so the command should be [root@managernode ~]# docker service create --name=viz --publish=8080:8080/tcp --constraint==node.role==manager --mount type=bind,src=/var/run/docker.sock,dst=/var/run/docker.sock dockersamples/visualizer Error response from daemon: rpc error: code = Unknown desc = constraint expected one operator from ==, !=

Issue:-  The issue occured while specifying docker to use the bindmount for the volume with following command docker service create --name=viz --publish=8080:8080/tcp --constraint=node.role==manager --mount=type=bind, src=/var/run/docker.sock,dst=/var/run/docker.sock dockersamples/visualizer Error:-   invalid argument "type=bind," for "--mount" flag: invalid field '' must be a key=value pair Resolution:- The issue is coming because there is a space between the , and src in the above command. Make sure there is no space between  mount=type=bind, src=/var/run/docker.sock like  mount=type=bind,src=/var/run/docker.sock  Than it should work fine. docker service create --name=viz --publish=8080:8080/tcp --constraint=node.role==manager --mount type=bind,src=/var/run/docker.sock,dst=/var/run/docker.sock dockersamples/visualizer