apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T11:40:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-102-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-102.ec2.internal uid: fac662f4-9c63-4e52-9eda-754ee886a71c resourceVersion: "22126" uid: 8c362e58-bfcf-45a2-8b41-203d40a32d97 spec: sourcePod: network-check-source-56499946bc-w84g8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-02T11:47: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.04896ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:47:45Z" - latency: 815.985µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:46:45Z" - latency: 1.113234ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:45:45Z" - latency: 833.069µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:44:45Z" - latency: 997.76µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:43:45Z" - latency: 965.716µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:42:45Z" - latency: 998.804µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:41:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T11:40:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-102-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-102.ec2.internal uid: fac662f4-9c63-4e52-9eda-754ee886a71c resourceVersion: "21117" uid: 439720e0-7e86-48f4-bdf8-f6108b60e1d3 spec: sourcePod: network-check-source-56499946bc-w84g8 targetEndpoint: a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T11:46:45Z" message: 'load-balancer-api-external: tcp connection to a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.473018ms message: 'load-balancer-api-external: tcp connection to a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:46:45Z" - latency: 7.431926ms message: 'load-balancer-api-external: resolved host name a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T11:46:45Z" - latency: 4.569734ms message: 'load-balancer-api-external: tcp connection to a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:45:45Z" - latency: 9.076208ms message: 'load-balancer-api-external: resolved host name a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T11:45:45Z" - latency: 4.460379ms message: 'load-balancer-api-external: tcp connection to a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:44:45Z" - latency: 9.909254ms message: 'load-balancer-api-external: resolved host name a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T11:44:45Z" - latency: 4.358375ms message: 'load-balancer-api-external: tcp connection to a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:43:45Z" - latency: 8.86191ms message: 'load-balancer-api-external: resolved host name a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T11:43:45Z" - latency: 4.846385ms message: 'load-balancer-api-external: tcp connection to a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:42:45Z" - latency: 6.760039ms message: 'load-balancer-api-external: resolved host name a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T11:42:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T11:40:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-102-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-102.ec2.internal uid: fac662f4-9c63-4e52-9eda-754ee886a71c resourceVersion: "21118" uid: 73db910a-d98b-4fe9-b5fa-1d15e8891110 spec: sourcePod: network-check-source-56499946bc-w84g8 targetEndpoint: a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T11:46:45Z" message: 'load-balancer-api-internal: tcp connection to a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.342253ms message: 'load-balancer-api-internal: tcp connection to a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:46:45Z" - latency: 7.44505ms message: 'load-balancer-api-internal: resolved host name a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T11:46:45Z" - latency: 4.520726ms message: 'load-balancer-api-internal: tcp connection to a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:45:45Z" - latency: 9.156656ms message: 'load-balancer-api-internal: resolved host name a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T11:45:45Z" - latency: 4.418885ms message: 'load-balancer-api-internal: tcp connection to a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:44:45Z" - latency: 9.973846ms message: 'load-balancer-api-internal: resolved host name a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T11:44:45Z" - latency: 4.39263ms message: 'load-balancer-api-internal: tcp connection to a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:43:45Z" - latency: 8.911613ms message: 'load-balancer-api-internal: resolved host name a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T11:43:45Z" - latency: 4.802976ms message: 'load-balancer-api-internal: tcp connection to a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:42:45Z" - latency: 6.810109ms message: 'load-balancer-api-internal: resolved host name a9b0166d85d264efab0b23d89062a331-a4af2453eebb491e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T11:42:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T11:40:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-102-to-network-check-target-ip-10-0-128-228 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-102.ec2.internal uid: fac662f4-9c63-4e52-9eda-754ee886a71c resourceVersion: "22125" uid: 71285576-a97b-4d1f-a5d0-123c2d2e3f7a spec: sourcePod: network-check-source-56499946bc-w84g8 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-02T11:47:45Z" message: 'network-check-target-ip-10-0-128-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.85061ms message: 'network-check-target-ip-10-0-128-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:47:45Z" - latency: 1.875813ms message: 'network-check-target-ip-10-0-128-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:46:45Z" - latency: 1.745086ms message: 'network-check-target-ip-10-0-128-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:45:45Z" - latency: 1.904806ms message: 'network-check-target-ip-10-0-128-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:44:45Z" - latency: 2.123559ms message: 'network-check-target-ip-10-0-128-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:43:45Z" - latency: 1.894743ms message: 'network-check-target-ip-10-0-128-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:42:45Z" - latency: 1.785808ms message: 'network-check-target-ip-10-0-128-228: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:41:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T11:40:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-102-to-network-check-target-ip-10-0-134-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-102.ec2.internal uid: fac662f4-9c63-4e52-9eda-754ee886a71c resourceVersion: "22123" uid: b2d758c0-bd95-4738-8268-baf0859f761a spec: sourcePod: network-check-source-56499946bc-w84g8 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-02T11:47:45Z" message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 762.842µs message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:47:45Z" - latency: 1.276918ms message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:46:45Z" - latency: 904.803µs message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:45:45Z" - latency: 1.125342ms message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:44:45Z" - latency: 1.664696ms message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:43:45Z" - latency: 767.469µs message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:42:45Z" - latency: 1.562259ms message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:41:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T11:40:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-102-to-network-check-target-ip-10-0-139-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-102.ec2.internal uid: fac662f4-9c63-4e52-9eda-754ee886a71c resourceVersion: "22124" uid: d225b209-a71d-4053-8cb6-3f8b4bf19c59 spec: sourcePod: network-check-source-56499946bc-w84g8 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-02T11:47:45Z" message: 'network-check-target-ip-10-0-139-160: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.050954ms message: 'network-check-target-ip-10-0-139-160: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:47:45Z" - latency: 1.943775ms message: 'network-check-target-ip-10-0-139-160: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:46:45Z" - latency: 2.096152ms message: 'network-check-target-ip-10-0-139-160: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:45:45Z" - latency: 2.16035ms message: 'network-check-target-ip-10-0-139-160: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:44:45Z" - latency: 2.128684ms message: 'network-check-target-ip-10-0-139-160: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:43:45Z" - latency: 2.114426ms message: 'network-check-target-ip-10-0-139-160: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:42:45Z" - latency: 2.482333ms message: 'network-check-target-ip-10-0-139-160: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:41:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T11:40:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-102-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-102.ec2.internal uid: fac662f4-9c63-4e52-9eda-754ee886a71c resourceVersion: "21116" uid: 248daa9a-f2a8-4bf8-8bbd-e3767269b788 spec: sourcePod: network-check-source-56499946bc-w84g8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-02T11:46:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 904.928µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:46:45Z" - latency: 2.321919ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T11:46:45Z" - latency: 907.122µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:45:45Z" - latency: 1.683772ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T11:45:45Z" - latency: 790.348µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:44:45Z" - latency: 2.27345ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T11:44:45Z" - latency: 869.766µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:43:45Z" - latency: 2.662975ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T11:43:45Z" - latency: 849µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T11:42:45Z" - latency: 1.723207ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T11:42:45Z" kind: List metadata: resourceVersion: ""