apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:41:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-27-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-27.ec2.internal uid: ab6e9698-ca67-4512-a386-4b2cc65ce554 resourceVersion: "33780" uid: 347749c0-6b0d-4f86-9ea4-1e545ebe932c spec: sourcePod: network-check-source-8894fc9bd-6mngq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-23T16:48:10Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.476673ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:02:10Z" - latency: 1.330366ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:01:10Z" - latency: 2.480176ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:00:10Z" - latency: 989.963µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:59:10Z" - latency: 1.148142ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:58:10Z" - latency: 757.617µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:57:10Z" - latency: 803.473µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:56:10Z" - latency: 1.257199ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:55:10Z" - latency: 1.189042ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:54:10Z" - latency: 1.433007ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:53:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:41:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-27-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-27.ec2.internal uid: ab6e9698-ca67-4512-a386-4b2cc65ce554 resourceVersion: "36302" uid: 0e0b1b61-8afc-4fb8-96eb-9e42ef8f7ee1 spec: sourcePod: network-check-source-8894fc9bd-6mngq targetEndpoint: a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T16:47:10Z" message: 'load-balancer-api-external: tcp connection to a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.969445ms message: 'load-balancer-api-external: tcp connection to a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:05:10Z" - latency: 8.03107ms message: 'load-balancer-api-external: resolved host name a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:05:10Z" - latency: 5.017711ms message: 'load-balancer-api-external: tcp connection to a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:04:10Z" - latency: 6.409374ms message: 'load-balancer-api-external: resolved host name a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:04:10Z" - latency: 4.487372ms message: 'load-balancer-api-external: tcp connection to a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:03:10Z" - latency: 7.535257ms message: 'load-balancer-api-external: resolved host name a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:03:10Z" - latency: 5.026469ms message: 'load-balancer-api-external: tcp connection to a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:02:10Z" - latency: 6.963013ms message: 'load-balancer-api-external: resolved host name a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:02:10Z" - latency: 5.049266ms message: 'load-balancer-api-external: tcp connection to a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:01:10Z" - latency: 7.049998ms message: 'load-balancer-api-external: resolved host name a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:01:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:41:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-27-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-27.ec2.internal uid: ab6e9698-ca67-4512-a386-4b2cc65ce554 resourceVersion: "36303" uid: 315548da-8dec-431c-be70-d9afb48f8559 spec: sourcePod: network-check-source-8894fc9bd-6mngq targetEndpoint: a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T16:47:10Z" message: 'load-balancer-api-internal: tcp connection to a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.955029ms message: 'load-balancer-api-internal: tcp connection to a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:05:10Z" - latency: 8.081151ms message: 'load-balancer-api-internal: resolved host name a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:05:10Z" - latency: 5.052113ms message: 'load-balancer-api-internal: tcp connection to a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:04:10Z" - latency: 6.515467ms message: 'load-balancer-api-internal: resolved host name a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:04:10Z" - latency: 5.135657ms message: 'load-balancer-api-internal: tcp connection to a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:03:10Z" - latency: 7.579678ms message: 'load-balancer-api-internal: resolved host name a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:03:10Z" - latency: 5.297807ms message: 'load-balancer-api-internal: tcp connection to a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:02:10Z" - latency: 6.965578ms message: 'load-balancer-api-internal: resolved host name a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:02:10Z" - latency: 4.845477ms message: 'load-balancer-api-internal: tcp connection to a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:01:10Z" - latency: 6.332033ms message: 'load-balancer-api-internal: resolved host name a5c3aba9edb4b4c27bda68b9af510bdd-558dc80b5eee43ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:01:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:41:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-27-to-network-check-target-ip-10-0-128-198 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-27.ec2.internal uid: ab6e9698-ca67-4512-a386-4b2cc65ce554 resourceVersion: "33779" uid: caa6fc93-908a-4ed3-ae3b-6cb3c265fb80 spec: sourcePod: network-check-source-8894fc9bd-6mngq targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-23T16:48:10Z" message: 'network-check-target-ip-10-0-128-198: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.095837ms message: 'network-check-target-ip-10-0-128-198: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:02:10Z" - latency: 2.242055ms message: 'network-check-target-ip-10-0-128-198: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:01:10Z" - latency: 3.006292ms message: 'network-check-target-ip-10-0-128-198: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:00:10Z" - latency: 2.356743ms message: 'network-check-target-ip-10-0-128-198: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:59:10Z" - latency: 2.323998ms message: 'network-check-target-ip-10-0-128-198: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:58:10Z" - latency: 2.170368ms message: 'network-check-target-ip-10-0-128-198: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:57:10Z" - latency: 1.820509ms message: 'network-check-target-ip-10-0-128-198: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:56:10Z" - latency: 2.302017ms message: 'network-check-target-ip-10-0-128-198: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:55:10Z" - latency: 1.983762ms message: 'network-check-target-ip-10-0-128-198: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:54:10Z" - latency: 2.092191ms message: 'network-check-target-ip-10-0-128-198: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:53:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:41:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-27-to-network-check-target-ip-10-0-136-190 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-27.ec2.internal uid: ab6e9698-ca67-4512-a386-4b2cc65ce554 resourceVersion: "33778" uid: 28bc7a4f-c9e9-44bd-a552-c7a5fc091a9b spec: sourcePod: network-check-source-8894fc9bd-6mngq targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-23T16:48:10Z" message: 'network-check-target-ip-10-0-136-190: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.008574ms message: 'network-check-target-ip-10-0-136-190: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:02:10Z" - latency: 1.979075ms message: 'network-check-target-ip-10-0-136-190: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:01:10Z" - latency: 2.901998ms message: 'network-check-target-ip-10-0-136-190: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:00:10Z" - latency: 1.824186ms message: 'network-check-target-ip-10-0-136-190: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:59:10Z" - latency: 1.737907ms message: 'network-check-target-ip-10-0-136-190: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:58:10Z" - latency: 1.793708ms message: 'network-check-target-ip-10-0-136-190: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:57:10Z" - latency: 1.800825ms message: 'network-check-target-ip-10-0-136-190: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:56:10Z" - latency: 1.910322ms message: 'network-check-target-ip-10-0-136-190: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:55:10Z" - latency: 1.778197ms message: 'network-check-target-ip-10-0-136-190: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:54:10Z" - latency: 2.095039ms message: 'network-check-target-ip-10-0-136-190: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:53:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:41:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-27-to-network-check-target-ip-10-0-136-27 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-27.ec2.internal uid: ab6e9698-ca67-4512-a386-4b2cc65ce554 resourceVersion: "33777" uid: b83212ac-b031-4ab4-a631-aa1116af062c spec: sourcePod: network-check-source-8894fc9bd-6mngq targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-23T16:48:10Z" message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 914.229µs message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:02:10Z" - latency: 1.465281ms message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:01:10Z" - latency: 2.554691ms message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:00:10Z" - latency: 1.610553ms message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:59:10Z" - latency: 1.324393ms message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:58:10Z" - latency: 1.004535ms message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:57:10Z" - latency: 989.73µs message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:56:10Z" - latency: 919.441µs message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:55:10Z" - latency: 949.588µs message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:54:10Z" - latency: 795.244µs message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T16:53:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:41:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-27-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-27.ec2.internal uid: ab6e9698-ca67-4512-a386-4b2cc65ce554 resourceVersion: "36301" uid: 623d3a83-c43f-4e3f-a83d-96c0287387e9 spec: sourcePod: network-check-source-8894fc9bd-6mngq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-23T16:47:10Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.459179ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:05:10Z" - latency: 1.763578ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T17:05:10Z" - latency: 928.997µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:04:10Z" - latency: 1.992877ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T17:04:10Z" - latency: 1.104287ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:03:10Z" - latency: 2.08646ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T17:03:10Z" - latency: 823.11µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:02:10Z" - latency: 1.992826ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T17:02:10Z" - latency: 14.751719ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:01:10Z" - latency: 1.849168ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T17:01:10Z" kind: List metadata: resourceVersion: ""