apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:15:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-215-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-215.ec2.internal uid: 5d2528fa-f8f7-4738-88e9-08df6818fe51 resourceVersion: "20409" uid: a77ac0fc-0849-442c-bc8d-02aa73bd1ca6 spec: sourcePod: network-check-source-7d88cb55d8-q247t targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T17:22:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.066938ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:36:25Z" - latency: 1.197548ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:35:25Z" - latency: 1.066262ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:34:25Z" - latency: 962.601µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:33:25Z" - latency: 1.48389ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:32:25Z" - latency: 947.219µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:31:25Z" - latency: 896.063µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:30:25Z" - latency: 1.172363ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:29:25Z" - latency: 1.018752ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:28:25Z" - latency: 1.041189ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:27:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:15:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-215-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-215.ec2.internal uid: 5d2528fa-f8f7-4738-88e9-08df6818fe51 resourceVersion: "21872" uid: c9a54518-cd26-45e0-bd34-6112f7b42bd0 spec: sourcePod: network-check-source-7d88cb55d8-q247t targetEndpoint: a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T17:21:25Z" message: 'load-balancer-api-external: tcp connection to a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.729121ms message: 'load-balancer-api-external: tcp connection to a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:39:25Z" - latency: 8.192599ms message: 'load-balancer-api-external: resolved host name a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:39:25Z" - latency: 5.485379ms message: 'load-balancer-api-external: tcp connection to a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:38:25Z" - latency: 9.163339ms message: 'load-balancer-api-external: resolved host name a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:38:25Z" - latency: 5.539346ms message: 'load-balancer-api-external: tcp connection to a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:37:25Z" - latency: 7.695291ms message: 'load-balancer-api-external: resolved host name a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:37:25Z" - latency: 4.663451ms message: 'load-balancer-api-external: tcp connection to a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:36:25Z" - latency: 8.973387ms message: 'load-balancer-api-external: resolved host name a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:36:25Z" - latency: 6.613426ms message: 'load-balancer-api-external: tcp connection to a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:35:25Z" - latency: 7.739195ms message: 'load-balancer-api-external: resolved host name a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:35:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:15:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-215-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-215.ec2.internal uid: 5d2528fa-f8f7-4738-88e9-08df6818fe51 resourceVersion: "21871" uid: 96c3429d-4966-42bd-be29-6a4d8cd346d5 spec: sourcePod: network-check-source-7d88cb55d8-q247t targetEndpoint: a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T17:21:25Z" message: 'load-balancer-api-internal: tcp connection to a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.642213ms message: 'load-balancer-api-internal: tcp connection to a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:39:25Z" - latency: 8.280502ms message: 'load-balancer-api-internal: resolved host name a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:39:25Z" - latency: 5.498954ms message: 'load-balancer-api-internal: tcp connection to a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:38:25Z" - latency: 9.219631ms message: 'load-balancer-api-internal: resolved host name a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:38:25Z" - latency: 6.338501ms message: 'load-balancer-api-internal: tcp connection to a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:37:25Z" - latency: 7.723525ms message: 'load-balancer-api-internal: resolved host name a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:37:25Z" - latency: 6.506978ms message: 'load-balancer-api-internal: tcp connection to a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:36:25Z" - latency: 8.918982ms message: 'load-balancer-api-internal: resolved host name a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:36:25Z" - latency: 6.684354ms message: 'load-balancer-api-internal: tcp connection to a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:35:25Z" - latency: 7.711699ms message: 'load-balancer-api-internal: resolved host name a5d375db654b24190969bb09250ff45d-032a492951f3777e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:35:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:15:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-215-to-network-check-target-ip-10-0-136-213 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-215.ec2.internal uid: 5d2528fa-f8f7-4738-88e9-08df6818fe51 resourceVersion: "20407" uid: cda1c4fa-1917-453e-92f2-111954ac5711 spec: sourcePod: network-check-source-7d88cb55d8-q247t targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:22:25Z" message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.363323ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:36:25Z" - latency: 2.416724ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:35:25Z" - latency: 2.293825ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:34:25Z" - latency: 2.14754ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:33:25Z" - latency: 2.162466ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:32:25Z" - latency: 2.020683ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:31:25Z" - latency: 2.281556ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:30:25Z" - latency: 2.483588ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:29:25Z" - latency: 2.270928ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:28:25Z" - latency: 2.108771ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:27:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:15:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-215-to-network-check-target-ip-10-0-136-215 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-215.ec2.internal uid: 5d2528fa-f8f7-4738-88e9-08df6818fe51 resourceVersion: "20406" uid: f3ed5de2-39a1-42c1-af67-257fab875730 spec: sourcePod: network-check-source-7d88cb55d8-q247t targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:22:25Z" message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.126553ms message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:36:25Z" - latency: 903.033µs message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:35:25Z" - latency: 1.354287ms message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:34:25Z" - latency: 1.277491ms message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:33:25Z" - latency: 848.921µs message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:32:25Z" - latency: 852.391µs message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:31:25Z" - latency: 922.269µs message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:30:25Z" - latency: 1.502125ms message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:29:25Z" - latency: 1.383315ms message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:28:25Z" - latency: 890.641µs message: 'network-check-target-ip-10-0-136-215: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:27:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:15:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-215-to-network-check-target-ip-10-0-141-34 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-215.ec2.internal uid: 5d2528fa-f8f7-4738-88e9-08df6818fe51 resourceVersion: "20408" uid: f39c4d32-c751-46ec-804e-024b8ef4b538 spec: sourcePod: network-check-source-7d88cb55d8-q247t targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:22:25Z" message: 'network-check-target-ip-10-0-141-34: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.131709ms message: 'network-check-target-ip-10-0-141-34: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:36:25Z" - latency: 2.255992ms message: 'network-check-target-ip-10-0-141-34: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:35:25Z" - latency: 2.278561ms message: 'network-check-target-ip-10-0-141-34: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:34:25Z" - latency: 2.336908ms message: 'network-check-target-ip-10-0-141-34: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:33:25Z" - latency: 2.755372ms message: 'network-check-target-ip-10-0-141-34: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:32:25Z" - latency: 2.362748ms message: 'network-check-target-ip-10-0-141-34: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:31:25Z" - latency: 2.31521ms message: 'network-check-target-ip-10-0-141-34: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:30:25Z" - latency: 2.468234ms message: 'network-check-target-ip-10-0-141-34: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:29:25Z" - latency: 2.551845ms message: 'network-check-target-ip-10-0-141-34: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:28:25Z" - latency: 2.023393ms message: 'network-check-target-ip-10-0-141-34: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:27:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:15:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-215-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-215.ec2.internal uid: 5d2528fa-f8f7-4738-88e9-08df6818fe51 resourceVersion: "21870" uid: aae4a6fb-d9ef-4645-a043-7bb1d10824f6 spec: sourcePod: network-check-source-7d88cb55d8-q247t targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T17:21:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.425136ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:39:25Z" - latency: 1.814608ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:39:25Z" - latency: 873.186µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:38:25Z" - latency: 1.817947ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:38:25Z" - latency: 1.107386ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:37:25Z" - latency: 1.683639ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:37:25Z" - latency: 1.112031ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:36:25Z" - latency: 1.944314ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:36:25Z" - latency: 967.289µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:35:25Z" - latency: 1.701873ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:35:25Z" kind: List metadata: resourceVersion: ""