Skip to main content

Kubernetess - You must be logged in to the server (Unauthorized):

Kubernetes - You must be logged in to the server (Unauthorized):

Check expiration of the certificates:
#kubeadm alpha certs check-expiration OR

find /etc/kubernetes/pki/ -type f -name "*.crt" -print|egrep -v 'ca.crt$'|xargs -L 1 -t -i bash -c 'openssl x509 -noout -text -in {}|grep After'

Renew all certificates:
#kubeadm alpha certs renew all

Check expiration of the certificates:
#kubeadm alpha certs check-expiration

Backup existing config file:
#cat cp /etc/kubernetes/admin.conf $HOME/.kube/config > cp /etc/kubernetes/admin.conf.orig

Replace the config file
#cp /etc/kubernetes/admin.conf $HOME/.kube/config

#kubectl get pods --all-namespaces
NAMESPACE     NAME                                             READY   STATUS    RESTARTS   AGE
kube-system   coredns-66bff467f8-djhr7                         1/1     Running   1          450d
kube-system   coredns-66bff467f8-dn2t5                         1/1     Running   1          450d
kube-system   etcd-usg-dt-mysql03.wdc.com                      1/1     Running   0          16m
kube-system   kube-apiserver-<hostname>                           1/1     Running   0          16m
kube-system   kube-controller-manager-<hostname>                  1/1     Running   0          16m
kube-system   kube-proxy-ktp6x                                 1/1     Running   0          450d
kube-system   kube-proxy-xs8bx                                 1/1     Running   1          450d
kube-system   kube-scheduler-<hostname>                           1/1     Running   0          16m
kube-system   weave-net-czmjs                                  2/2     Running   3          450d
kube-system   weave-net-g5vmn                                  2/2     Running   1          450d

Explore Kubernetes commands

Labels

Labels:
Location: San Francisco, CA, USA

Comments

Post a Comment

Popular posts from this blog

MySQL InnoDB cluster troubleshooting | commands

Cluster Validation: select * from performance_schema.replication_group_members; All members should be online. select instance_name, mysql_server_uuid, addresses from  mysql_innodb_cluster_metadata.instances; All instances should return same value for mysql_server_uuid SELECT @@GTID_EXECUTED; All nodes should return same value Frequently use commands: mysql> SET SQL_LOG_BIN = 0;  mysql> stop group_replication; mysql> set global super_read_only=0; mysql> drop database mysql_innodb_cluster_metadata; mysql> RESET MASTER; mysql> RESET SLAVE ALL; JS > var cluster = dba.getCluster() JS > var cluster = dba.getCluster("<Cluster_name>") JS > var cluster = dba.createCluster('name') JS > cluster.removeInstance('root@<IP_Address>:<Port_No>',{force: true}) JS > cluster.addInstance('root@<IP add>,:<port>') JS > cluster.addInstance('root@ <IP add>,:<port> ') JS > dba.getC...
Post a Comment
Read more

InnoDB cluster Remove Instance Force | Add InnoDB instance

InnoDB cluster environment UUID is different on node: To fix it stop group replication, remove instance (use force if require), add instance back Identify the node which is not in sync: Execute following SQL statement on each node and identify the node has different UUID on all nodes. mysql> select * from mysql_innodb_cluster_metadata.instances; Stop group replication: Stop group replication on the node which does not have same UUID on all nodes. mysql > stop GROUP_REPLICATION; Remove instances from cluster: Remove all secondary node from the cluster and add them back if require. $mysqlsh JS >\c root@<IP_Address>:<Port_No> JS > dba.getCluster().status() JS > dba.getCluster () <Cluster:cluster_name> JS > var cluster = dba.getCluster("cluster_name"); JS >  cluster.removeInstance('root@<IP_Address>:<Port_No>'); If you get "Cluster.removeInstance: Timeout reached waiting......" JS > cluster.removeInstance(...
2 comments
Read more

Oracle E-Business Suite Online Patch Phases executing adop

Following description about Oracle E-Business Suite is high level and from documentation https://docs.oracle.com/cd/E26401_01/doc.122/e22954/T202991T531062.htm#5281339 for in depth and detail description refer it. The online patching cycle phases: Prepare Apply Finalize Cutover Cleanup Prepare phase: Start a new online patching cycle, Prepares the environment for patching. $ adop phase=prepare Apply phase: Applies the specified patches to the environment. Apply one or more patches to the patch edition. $ adop phase=apply patches=123456,789101 workers=8 Finalize phase: Performs any final steps required to make the system ready for cutover. Perform the final patching operations that can be executed while the application is still online. $ adop phase=finalize Cutover phase: Shuts down application tier services, makes the patch edition the new run edition, and then restarts application tier services. This is the only phase that involves a brief ...
Post a Comment
Read more