Description of problem: `oc set probe` doesn't support setting startup probes. It supports liveness and readiness checks, but not startup probes. Version-Release number of selected component (if applicable): Checked with `oc` 4.3.23-202005230952-4fb2d4d and 4.4.0-202005290638-1960dd7: $ oc version Client Version: 4.3.23-202005230952-4fb2d4d Server Version: 4.3.18 Kubernetes Version: v1.16.2 How reproducible: 100% Steps to Reproduce: 1. run oc set probe --help Actual results: No flag for setting start probes. Expected results: Command should support --startup or similar flag. Additional info: Startup probes were introduced with Kubernetes 1.16, included in OCP 4.3.
checked with oc version --client -o yaml clientVersion: buildDate: "2020-06-22T17:36:51Z" compiler: gc gitCommit: b644a4b43e8d1cd9fa003e7686ce19454f456d08 gitTreeState: clean gitVersion: 4.6.0-202006221729.p0-b644a4b goVersion: go1.13.4 major: "" minor: "" platform: linux/amd64 The issue has fixed; [zhouying@dhcp-140-138 ~]$ oc set probe -h Set or remove a liveness, readiness or startup probe from a pod or pod template ..... # Set an HTTP startup probe for port 8080 and path /healthz over HTTP on the pod IP oc set probe dc/webapp --startup --get-url=http://:8080/healthz --startup=false: Set or remove a startup probe to verify this container is running [zhouying@dhcp-140-138 ~]$ oc set probe deploy/mytest --startup --get-url=http://:8081/healthz deployment.apps/mytest probes updated [zhouying@dhcp-140-138 ~]$ oc get deploy/mytest -o yaml .... startupProbe: failureThreshold: 3 httpGet: path: /healthz port: 8081 scheme: HTTP
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196