apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T16:36:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-63-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-63.ec2.internal uid: 8f8d0181-cb78-4f1d-a519-c25ac9bb23dc resourceVersion: "43634" uid: 8024a7f0-6102-4426-8479-55768bd08127 spec: sourcePod: network-check-source-6947749cfc-tjtls targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-12T16:43:45Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.085827ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:04:45Z" - latency: 966.267µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:03:45Z" - latency: 904.122µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:02:45Z" - latency: 1.182709ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:01:45Z" - latency: 1.488141ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:00:45Z" - latency: 1.20869ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T16:59:45Z" - latency: 953.622µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T16:58:45Z" - latency: 903.017µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T16:57:45Z" - latency: 722.801µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T16:56:45Z" - latency: 1.282149ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T16:55:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T16:36:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-63-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-63.ec2.internal uid: 8f8d0181-cb78-4f1d-a519-c25ac9bb23dc resourceVersion: "45707" uid: d42dacfc-270b-498b-996b-b231b4f86c77 spec: sourcePod: network-check-source-6947749cfc-tjtls targetEndpoint: a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T16:42:45Z" message: 'load-balancer-api-external: tcp connection to a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.060596ms message: 'load-balancer-api-external: tcp connection to a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:06:45Z" - latency: 8.558731ms message: 'load-balancer-api-external: resolved host name a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T17:06:45Z" - latency: 3.572733ms message: 'load-balancer-api-external: tcp connection to a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:05:45Z" - latency: 8.157924ms message: 'load-balancer-api-external: resolved host name a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T17:05:45Z" - latency: 5.689666ms message: 'load-balancer-api-external: tcp connection to a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:04:45Z" - latency: 8.303449ms message: 'load-balancer-api-external: resolved host name a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T17:04:45Z" - latency: 4.015944ms message: 'load-balancer-api-external: tcp connection to a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:03:45Z" - latency: 7.814549ms message: 'load-balancer-api-external: resolved host name a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T17:03:45Z" - latency: 3.60388ms message: 'load-balancer-api-external: tcp connection to a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:02:45Z" - latency: 8.681663ms message: 'load-balancer-api-external: resolved host name a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T17:02:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T16:36:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-63-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-63.ec2.internal uid: 8f8d0181-cb78-4f1d-a519-c25ac9bb23dc resourceVersion: "45706" uid: 6574a54b-4766-4b51-8ae5-f1add395b060 spec: sourcePod: network-check-source-6947749cfc-tjtls targetEndpoint: a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T16:42:45Z" message: 'load-balancer-api-internal: tcp connection to a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.26603ms message: 'load-balancer-api-internal: tcp connection to a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:06:45Z" - latency: 8.653723ms message: 'load-balancer-api-internal: resolved host name a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T17:06:45Z" - latency: 22.869546ms message: 'load-balancer-api-internal: tcp connection to a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:05:45Z" - latency: 8.132128ms message: 'load-balancer-api-internal: resolved host name a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T17:05:45Z" - latency: 4.837614ms message: 'load-balancer-api-internal: tcp connection to a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:04:45Z" - latency: 8.390551ms message: 'load-balancer-api-internal: resolved host name a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T17:04:45Z" - latency: 4.023878ms message: 'load-balancer-api-internal: tcp connection to a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:03:45Z" - latency: 7.768141ms message: 'load-balancer-api-internal: resolved host name a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T17:03:45Z" - latency: 3.58678ms message: 'load-balancer-api-internal: tcp connection to a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:02:45Z" - latency: 8.755066ms message: 'load-balancer-api-internal: resolved host name a4860e4816bdc47ccb0472515c07acb2-0f9d668d329a42a8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T17:02:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T16:36:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-63-to-network-check-target-ip-10-0-130-140 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-63.ec2.internal uid: 8f8d0181-cb78-4f1d-a519-c25ac9bb23dc resourceVersion: "43633" uid: b4c7cf69-f56e-4a05-8053-c079a17a36a5 spec: sourcePod: network-check-source-6947749cfc-tjtls targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-12T16:43:45Z" message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.315102ms message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:04:45Z" - latency: 2.637845ms message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:03:45Z" - latency: 2.418816ms message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:02:45Z" - latency: 2.305068ms message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:01:45Z" - latency: 2.302464ms message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:00:45Z" - latency: 2.350505ms message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T16:59:45Z" - latency: 2.125464ms message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T16:58:45Z" - latency: 2.515763ms message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T16:57:45Z" - latency: 2.010625ms message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T16:56:45Z" - latency: 2.254989ms message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T16:55:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T16:36:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-63-to-network-check-target-ip-10-0-131-155 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-63.ec2.internal uid: 8f8d0181-cb78-4f1d-a519-c25ac9bb23dc resourceVersion: "43632" uid: a67867fc-1496-4da8-ad3a-d2ae72927c1c spec: sourcePod: network-check-source-6947749cfc-tjtls targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-12T16:43:45Z" message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.323533ms message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:04:45Z" - latency: 2.169594ms message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:03:45Z" - latency: 2.090023ms message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:02:45Z" - latency: 2.013615ms message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:01:45Z" - latency: 1.799739ms message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:00:45Z" - latency: 1.525337ms message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T16:59:45Z" - latency: 2.056383ms message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T16:58:45Z" - latency: 2.477534ms message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T16:57:45Z" - latency: 1.448813ms message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T16:56:45Z" - latency: 1.73141ms message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T16:55:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T16:36:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-63-to-network-check-target-ip-10-0-132-63 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-63.ec2.internal uid: 8f8d0181-cb78-4f1d-a519-c25ac9bb23dc resourceVersion: "43631" uid: 41471692-1aa3-4370-b97d-970e9e944ebd spec: sourcePod: network-check-source-6947749cfc-tjtls targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-12T16:43:45Z" message: 'network-check-target-ip-10-0-132-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 939.586µs message: 'network-check-target-ip-10-0-132-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:04:45Z" - latency: 1.222147ms message: 'network-check-target-ip-10-0-132-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:03:45Z" - latency: 871.645µs message: 'network-check-target-ip-10-0-132-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:02:45Z" - latency: 931.879µs message: 'network-check-target-ip-10-0-132-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:01:45Z" - latency: 1.036042ms message: 'network-check-target-ip-10-0-132-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:00:45Z" - latency: 789.821µs message: 'network-check-target-ip-10-0-132-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T16:59:45Z" - latency: 821.256µs message: 'network-check-target-ip-10-0-132-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T16:58:45Z" - latency: 777.573µs message: 'network-check-target-ip-10-0-132-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T16:57:45Z" - latency: 942.733µs message: 'network-check-target-ip-10-0-132-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T16:56:45Z" - latency: 1.017722ms message: 'network-check-target-ip-10-0-132-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T16:55:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T16:36:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-63-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-63.ec2.internal uid: 8f8d0181-cb78-4f1d-a519-c25ac9bb23dc resourceVersion: "45705" uid: ae12a154-38da-418b-9dd1-8ed1d3f85737 spec: sourcePod: network-check-source-6947749cfc-tjtls targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-12T16:42:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 860.978µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:06:45Z" - latency: 1.522324ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T17:06:45Z" - latency: 890.388µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:05:45Z" - latency: 1.858242ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T17:05:45Z" - latency: 960.76µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:04:45Z" - latency: 1.761323ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T17:04:45Z" - latency: 1.017312ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:03:45Z" - latency: 2.103482ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T17:03:45Z" - latency: 922.4µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T17:02:45Z" - latency: 1.792513ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T17:02:45Z" kind: List metadata: resourceVersion: ""