apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:26:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-115-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-115.ec2.internal uid: 20b02451-da41-474d-9d67-01c0bc0b357e resourceVersion: "54147" uid: 9e02e122-270a-4647-ba38-e82f6f252e42 spec: sourcePod: network-check-source-989f8b8dc-hw5k6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-02T23:33:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.006298ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T00:01:55Z" - latency: 861.148µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-03T00:00:55Z" - latency: 1.294295ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:59:55Z" - latency: 1.199085ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:58:55Z" - latency: 1.351507ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:57:55Z" - latency: 1.177416ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:56:55Z" - latency: 1.059552ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:55:55Z" - latency: 992.003µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:54:55Z" - latency: 932.416µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:53:55Z" - latency: 1.125103ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:52:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:26:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-115-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-115.ec2.internal uid: 20b02451-da41-474d-9d67-01c0bc0b357e resourceVersion: "55043" uid: 63b6cb33-6a88-40ab-a676-650cd353bc9d spec: sourcePod: network-check-source-989f8b8dc-hw5k6 targetEndpoint: a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T23:32:55Z" message: 'load-balancer-api-external: tcp connection to a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.608969ms message: 'load-balancer-api-external: tcp connection to a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T00:02:55Z" - latency: 9.04873ms message: 'load-balancer-api-external: resolved host name a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T00:02:55Z" - latency: 4.346239ms message: 'load-balancer-api-external: tcp connection to a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T00:01:55Z" - latency: 7.574347ms message: 'load-balancer-api-external: resolved host name a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T00:01:55Z" - latency: 5.317234ms message: 'load-balancer-api-external: tcp connection to a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T00:00:55Z" - latency: 7.536798ms message: 'load-balancer-api-external: resolved host name a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T00:00:55Z" - latency: 4.952627ms message: 'load-balancer-api-external: tcp connection to a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:59:55Z" - latency: 6.784252ms message: 'load-balancer-api-external: resolved host name a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:59:55Z" - latency: 5.464315ms message: 'load-balancer-api-external: tcp connection to a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:58:55Z" - latency: 9.59445ms message: 'load-balancer-api-external: resolved host name a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:58:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:26:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-115-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-115.ec2.internal uid: 20b02451-da41-474d-9d67-01c0bc0b357e resourceVersion: "55042" uid: 1bc0e90c-f81e-41a4-97ca-d00a8c06a154 spec: sourcePod: network-check-source-989f8b8dc-hw5k6 targetEndpoint: a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T23:32:55Z" message: 'load-balancer-api-internal: tcp connection to a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.003018ms message: 'load-balancer-api-internal: tcp connection to a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T00:02:55Z" - latency: 8.958153ms message: 'load-balancer-api-internal: resolved host name a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T00:02:55Z" - latency: 4.320281ms message: 'load-balancer-api-internal: tcp connection to a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T00:01:55Z" - latency: 7.456868ms message: 'load-balancer-api-internal: resolved host name a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T00:01:55Z" - latency: 5.417315ms message: 'load-balancer-api-internal: tcp connection to a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-03T00:00:55Z" - latency: 7.58021ms message: 'load-balancer-api-internal: resolved host name a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-03T00:00:55Z" - latency: 4.607518ms message: 'load-balancer-api-internal: tcp connection to a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:59:55Z" - latency: 6.746298ms message: 'load-balancer-api-internal: resolved host name a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:59:55Z" - latency: 5.694479ms message: 'load-balancer-api-internal: tcp connection to a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:58:55Z" - latency: 9.458186ms message: 'load-balancer-api-internal: resolved host name a0950bfa8e5c54197b06a68915e58bc7-c1668bc45e191304.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:58:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:26:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-115-to-network-check-target-ip-10-0-130-115 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-115.ec2.internal uid: 20b02451-da41-474d-9d67-01c0bc0b357e resourceVersion: "54145" uid: b4d864e9-dab6-4ae9-b528-7b793f3460c2 spec: sourcePod: network-check-source-989f8b8dc-hw5k6 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-02T23:33:55Z" message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.363055ms message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T00:01:55Z" - latency: 973.764µs message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T00:00:55Z" - latency: 902.196µs message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:59:55Z" - latency: 1.497046ms message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:58:55Z" - latency: 1.349075ms message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:57:55Z" - latency: 1.12757ms message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:56:55Z" - latency: 877.787µs message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:55:55Z" - latency: 1.53862ms message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:54:55Z" - latency: 947.958µs message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:53:55Z" - latency: 1.09305ms message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:52:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:26:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-115-to-network-check-target-ip-10-0-130-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-115.ec2.internal uid: 20b02451-da41-474d-9d67-01c0bc0b357e resourceVersion: "54144" uid: 5c86ab37-cf87-4c84-887f-18f9e6187300 spec: sourcePod: network-check-source-989f8b8dc-hw5k6 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-02T23:33:55Z" message: 'network-check-target-ip-10-0-130-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.251701ms message: 'network-check-target-ip-10-0-130-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T00:01:55Z" - latency: 1.871941ms message: 'network-check-target-ip-10-0-130-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T00:00:55Z" - latency: 2.08096ms message: 'network-check-target-ip-10-0-130-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:59:55Z" - latency: 1.773872ms message: 'network-check-target-ip-10-0-130-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:58:55Z" - latency: 1.728985ms message: 'network-check-target-ip-10-0-130-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:57:55Z" - latency: 2.169145ms message: 'network-check-target-ip-10-0-130-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:56:55Z" - latency: 1.911122ms message: 'network-check-target-ip-10-0-130-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:55:55Z" - latency: 1.737415ms message: 'network-check-target-ip-10-0-130-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:54:55Z" - latency: 1.880958ms message: 'network-check-target-ip-10-0-130-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:53:55Z" - latency: 1.723776ms message: 'network-check-target-ip-10-0-130-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:52:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:26:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-115-to-network-check-target-ip-10-0-137-14 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-115.ec2.internal uid: 20b02451-da41-474d-9d67-01c0bc0b357e resourceVersion: "54146" uid: 29efd361-31c0-4b1b-b899-4d9cf4c13884 spec: sourcePod: network-check-source-989f8b8dc-hw5k6 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-02T23:33:55Z" message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.11794ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T00:01:55Z" - latency: 1.98527ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-03T00:00:55Z" - latency: 2.02761ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:59:55Z" - latency: 2.13906ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:58:55Z" - latency: 2.056838ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:57:55Z" - latency: 1.778037ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:56:55Z" - latency: 2.157509ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:55:55Z" - latency: 2.187452ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:54:55Z" - latency: 1.916553ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:53:55Z" - latency: 2.272302ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:52:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:26:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-115-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-115.ec2.internal uid: 20b02451-da41-474d-9d67-01c0bc0b357e resourceVersion: "55040" uid: 0bd9ae63-a933-4f7d-826e-fb044b127daa spec: sourcePod: network-check-source-989f8b8dc-hw5k6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-02T23:32:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 887.745µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-03T00:02:55Z" - latency: 1.602081ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-03T00:02:55Z" - latency: 881.798µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-03T00:01:55Z" - latency: 1.695865ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-03T00:01:55Z" - latency: 860.431µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-03T00:00:55Z" - latency: 1.955976ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-03T00:00:55Z" - latency: 933.822µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:59:55Z" - latency: 1.787319ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T23:59:55Z" - latency: 1.073512ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:58:55Z" - latency: 2.130391ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T23:58:55Z" kind: List metadata: resourceVersion: ""