apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T05:05:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-241-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-241.ec2.internal uid: ed7c59f9-d210-40e6-b6e3-e41d2434f0ec resourceVersion: "62068" uid: 54e3f52b-2721-4754-9bfc-3208162a7161 spec: sourcePod: network-check-source-869dcfcdcd-nlnw8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T05:12:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.020578ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:47:59Z" - latency: 948.403µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:46:59Z" - latency: 927.468µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:45:59Z" - latency: 1.283934ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:44:59Z" - latency: 1.256924ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:43:59Z" - latency: 829.091µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:42:59Z" - latency: 1.025411ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:41:59Z" - latency: 1.165937ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:40:59Z" - latency: 1.200329ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:39:59Z" - latency: 1.44646ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:38:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T05:05:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-241-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-241.ec2.internal uid: ed7c59f9-d210-40e6-b6e3-e41d2434f0ec resourceVersion: "62071" uid: 0251a3ca-9a13-44d7-9066-9443c8431de2 spec: sourcePod: network-check-source-869dcfcdcd-nlnw8 targetEndpoint: aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T05:11:59Z" message: 'load-balancer-api-external: tcp connection to aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.649006ms message: 'load-balancer-api-external: tcp connection to aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:47:59Z" - latency: 7.413ms message: 'load-balancer-api-external: resolved host name aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T05:47:59Z" - latency: 4.733976ms message: 'load-balancer-api-external: tcp connection to aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:46:59Z" - latency: 8.163516ms message: 'load-balancer-api-external: resolved host name aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T05:46:59Z" - latency: 5.372405ms message: 'load-balancer-api-external: tcp connection to aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:45:59Z" - latency: 6.930139ms message: 'load-balancer-api-external: resolved host name aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T05:45:59Z" - latency: 3.562452ms message: 'load-balancer-api-external: tcp connection to aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:44:59Z" - latency: 8.00322ms message: 'load-balancer-api-external: resolved host name aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T05:44:59Z" - latency: 4.131521ms message: 'load-balancer-api-external: tcp connection to aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:43:59Z" - latency: 6.681428ms message: 'load-balancer-api-external: resolved host name aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T05:43:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T05:05:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-241-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-241.ec2.internal uid: ed7c59f9-d210-40e6-b6e3-e41d2434f0ec resourceVersion: "62070" uid: ad549abc-ee38-4290-bb50-a9d5da24c2d8 spec: sourcePod: network-check-source-869dcfcdcd-nlnw8 targetEndpoint: aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T05:11:59Z" message: 'load-balancer-api-internal: tcp connection to aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.028393ms message: 'load-balancer-api-internal: tcp connection to aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:47:59Z" - latency: 7.523121ms message: 'load-balancer-api-internal: resolved host name aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T05:47:59Z" - latency: 4.751521ms message: 'load-balancer-api-internal: tcp connection to aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:46:59Z" - latency: 8.182378ms message: 'load-balancer-api-internal: resolved host name aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T05:46:59Z" - latency: 3.909164ms message: 'load-balancer-api-internal: tcp connection to aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:45:59Z" - latency: 6.792309ms message: 'load-balancer-api-internal: resolved host name aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T05:45:59Z" - latency: 4.431154ms message: 'load-balancer-api-internal: tcp connection to aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:44:59Z" - latency: 7.966985ms message: 'load-balancer-api-internal: resolved host name aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T05:44:59Z" - latency: 5.251276ms message: 'load-balancer-api-internal: tcp connection to aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:43:59Z" - latency: 6.654421ms message: 'load-balancer-api-internal: resolved host name aa5ce1a1bbe34437eb36d575a47fe455-6741e1430ff1d667.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T05:43:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T05:05:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-241-to-network-check-target-ip-10-0-128-231 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-241.ec2.internal uid: ed7c59f9-d210-40e6-b6e3-e41d2434f0ec resourceVersion: "62064" uid: bbf1f9da-4c6c-44f5-b227-624bc68514a2 spec: sourcePod: network-check-source-869dcfcdcd-nlnw8 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T05:12:59Z" message: 'network-check-target-ip-10-0-128-231: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.119325ms message: 'network-check-target-ip-10-0-128-231: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:47:59Z" - latency: 1.983531ms message: 'network-check-target-ip-10-0-128-231: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:46:59Z" - latency: 1.963483ms message: 'network-check-target-ip-10-0-128-231: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:45:59Z" - latency: 2.397142ms message: 'network-check-target-ip-10-0-128-231: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:44:59Z" - latency: 1.960664ms message: 'network-check-target-ip-10-0-128-231: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:43:59Z" - latency: 1.962454ms message: 'network-check-target-ip-10-0-128-231: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:42:59Z" - latency: 2.329468ms message: 'network-check-target-ip-10-0-128-231: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:41:59Z" - latency: 2.202019ms message: 'network-check-target-ip-10-0-128-231: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:40:59Z" - latency: 2.026413ms message: 'network-check-target-ip-10-0-128-231: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:39:59Z" - latency: 2.471054ms message: 'network-check-target-ip-10-0-128-231: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:38:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T05:05:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-241-to-network-check-target-ip-10-0-130-29 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-241.ec2.internal uid: ed7c59f9-d210-40e6-b6e3-e41d2434f0ec resourceVersion: "62065" uid: 80957cc3-7b65-4824-b95b-0157ef2348fa spec: sourcePod: network-check-source-869dcfcdcd-nlnw8 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T05:12:59Z" message: 'network-check-target-ip-10-0-130-29: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.011674ms message: 'network-check-target-ip-10-0-130-29: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:47:59Z" - latency: 1.884361ms message: 'network-check-target-ip-10-0-130-29: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:46:59Z" - latency: 2.121892ms message: 'network-check-target-ip-10-0-130-29: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:45:59Z" - latency: 2.042171ms message: 'network-check-target-ip-10-0-130-29: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:44:59Z" - latency: 1.977218ms message: 'network-check-target-ip-10-0-130-29: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:43:59Z" - latency: 2.515916ms message: 'network-check-target-ip-10-0-130-29: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:42:59Z" - latency: 2.169473ms message: 'network-check-target-ip-10-0-130-29: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:41:59Z" - latency: 2.165534ms message: 'network-check-target-ip-10-0-130-29: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:40:59Z" - latency: 2.336737ms message: 'network-check-target-ip-10-0-130-29: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:39:59Z" - latency: 2.136405ms message: 'network-check-target-ip-10-0-130-29: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:38:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T05:05:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-241-to-network-check-target-ip-10-0-134-241 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-241.ec2.internal uid: ed7c59f9-d210-40e6-b6e3-e41d2434f0ec resourceVersion: "62063" uid: 94c09ddc-0664-493b-b58f-4d3b472ea121 spec: sourcePod: network-check-source-869dcfcdcd-nlnw8 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T05:12:59Z" message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.146596ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:47:59Z" - latency: 859.329µs message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:46:59Z" - latency: 1.009059ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:45:59Z" - latency: 950.643µs message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:44:59Z" - latency: 958.658µs message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:43:59Z" - latency: 1.005676ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:42:59Z" - latency: 1.112726ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:41:59Z" - latency: 1.079846ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:40:59Z" - latency: 1.035463ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:39:59Z" - latency: 1.01426ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:38:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T05:05:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-241-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-241.ec2.internal uid: ed7c59f9-d210-40e6-b6e3-e41d2434f0ec resourceVersion: "62067" uid: 9df0f9f8-5be1-445f-add3-dc96cd28b9a4 spec: sourcePod: network-check-source-869dcfcdcd-nlnw8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T05:11:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 934.336µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:47:59Z" - latency: 2.055005ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T05:47:59Z" - latency: 1.11224ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:46:59Z" - latency: 2.258845ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T05:46:59Z" - latency: 1.021186ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:45:59Z" - latency: 2.018117ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T05:45:59Z" - latency: 1.022498ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:44:59Z" - latency: 2.156558ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T05:44:59Z" - latency: 1.053932ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T05:43:59Z" - latency: 1.825471ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T05:43:59Z" kind: List metadata: resourceVersion: ""