noseka1

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: mount-nfs
rules:
- apiGroups:
  - security.openshift.io
  resources:
  - securitycontextconstraints
  verbs:

noseka1

Examples

$ kubectl get pods -o json
$ kubectl get pods -o jsonpath='{@}'
$ kubectl get pods -o jsonpath='{.items[0]}'
$ kubectl get pods -o jsonpath='{.items[0].metadata.name}'
$ kubectl get pods -o jsonpath="{.items[*]['metadata.name', 'status.capacity']}"
$ kubectl get pods -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.status.startTime}{"\n"}{end}'
$ kubectl get pods -o jsonpath='{.items[*].status.podIP}'

noseka1

Upgrading OpenShift 4 cluster

Related OpenShift documentation is Updating a cluster within a minor version by using the CLI.

Available upgrades are managed by https://github.com/openshift/cincinnati-graph-data/tree/master/channels.

Individual graph edges can be blocked by https://github.com/openshift/cincinnati-graph-data/tree/master/blocked-edges.

KCS that is dynamically built and communicates why edges are blocked: https://access.redhat.com/node/6103381

noseka1

Examples

$ oc get pod <POD_NAME> -o json | jq -r '.spec.volumes[] | select(.name=="config").secret.secretName'

References

JSONPath in kubectl CLI.md