apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T08:47:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-194-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-194.ec2.internal uid: 5164a00c-69bc-497c-a003-8c70b732b053 resourceVersion: "15032" uid: 8644abfa-37af-413f-9771-82ea9894caf8 spec: sourcePod: network-check-source-6f8b768455-rzdfq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-17T08:54:11Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.170296ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:54:11Z" - latency: 1.244161ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:53:11Z" - latency: 1.067243ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:52:11Z" - latency: 910.464µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:51:11Z" - latency: 1.005421ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:50:11Z" - latency: 982.599µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:49:11Z" - latency: 922.17µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:48:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T08:47:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-194-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-194.ec2.internal uid: 5164a00c-69bc-497c-a003-8c70b732b053 resourceVersion: "14526" uid: 4bce7756-31d0-447c-8918-5a8b56dacd2e spec: sourcePod: network-check-source-6f8b768455-rzdfq targetEndpoint: a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T08:53:11Z" message: 'load-balancer-api-external: tcp connection to a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.680569ms message: 'load-balancer-api-external: tcp connection to a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:53:11Z" - latency: 8.169391ms message: 'load-balancer-api-external: resolved host name a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T08:53:11Z" - latency: 5.401418ms message: 'load-balancer-api-external: tcp connection to a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:52:11Z" - latency: 8.618894ms message: 'load-balancer-api-external: resolved host name a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T08:52:11Z" - latency: 5.580426ms message: 'load-balancer-api-external: tcp connection to a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:51:11Z" - latency: 7.421206ms message: 'load-balancer-api-external: resolved host name a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T08:51:11Z" - latency: 5.484587ms message: 'load-balancer-api-external: tcp connection to a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:50:11Z" - latency: 9.529325ms message: 'load-balancer-api-external: resolved host name a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T08:50:11Z" - latency: 3.9917ms message: 'load-balancer-api-external: tcp connection to a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:49:11Z" - latency: 7.932646ms message: 'load-balancer-api-external: resolved host name a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T08:49:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T08:47:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-194-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-194.ec2.internal uid: 5164a00c-69bc-497c-a003-8c70b732b053 resourceVersion: "14525" uid: 46ec2086-da9d-4b57-b5ed-689dc9f73513 spec: sourcePod: network-check-source-6f8b768455-rzdfq targetEndpoint: a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T08:53:11Z" message: 'load-balancer-api-internal: tcp connection to a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.69537ms message: 'load-balancer-api-internal: tcp connection to a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:53:11Z" - latency: 8.141574ms message: 'load-balancer-api-internal: resolved host name a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T08:53:11Z" - latency: 4.956013ms message: 'load-balancer-api-internal: tcp connection to a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:52:11Z" - latency: 8.696971ms message: 'load-balancer-api-internal: resolved host name a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T08:52:11Z" - latency: 5.522385ms message: 'load-balancer-api-internal: tcp connection to a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:51:11Z" - latency: 7.443601ms message: 'load-balancer-api-internal: resolved host name a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T08:51:11Z" - latency: 5.510187ms message: 'load-balancer-api-internal: tcp connection to a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:50:11Z" - latency: 9.491352ms message: 'load-balancer-api-internal: resolved host name a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T08:50:11Z" - latency: 4.034068ms message: 'load-balancer-api-internal: tcp connection to a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:49:11Z" - latency: 7.920971ms message: 'load-balancer-api-internal: resolved host name a8f30ef5ff2e442d6a344809f97dba1a-568d1c729364c752.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T08:49:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T08:47:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-194-to-network-check-target-ip-10-0-134-194 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-194.ec2.internal uid: 5164a00c-69bc-497c-a003-8c70b732b053 resourceVersion: "15029" uid: edacc44c-d407-4dd9-b2e9-f748aea6428c spec: sourcePod: network-check-source-6f8b768455-rzdfq targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-17T08:54:11Z" message: 'network-check-target-ip-10-0-134-194: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.658972ms message: 'network-check-target-ip-10-0-134-194: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:54:11Z" - latency: 1.287769ms message: 'network-check-target-ip-10-0-134-194: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:53:11Z" - latency: 1.545867ms message: 'network-check-target-ip-10-0-134-194: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:52:11Z" - latency: 1.303439ms message: 'network-check-target-ip-10-0-134-194: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:51:11Z" - latency: 1.418625ms message: 'network-check-target-ip-10-0-134-194: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:50:11Z" - latency: 1.202252ms message: 'network-check-target-ip-10-0-134-194: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:49:11Z" - latency: 1.263481ms message: 'network-check-target-ip-10-0-134-194: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:48:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T08:47:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-194-to-network-check-target-ip-10-0-138-83 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-194.ec2.internal uid: 5164a00c-69bc-497c-a003-8c70b732b053 resourceVersion: "15030" uid: ac169ffc-cd09-4ea1-8b44-3adbe88d592e spec: sourcePod: network-check-source-6f8b768455-rzdfq targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-17T08:54:11Z" message: 'network-check-target-ip-10-0-138-83: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.468415ms message: 'network-check-target-ip-10-0-138-83: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:54:11Z" - latency: 2.184042ms message: 'network-check-target-ip-10-0-138-83: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:53:11Z" - latency: 2.398148ms message: 'network-check-target-ip-10-0-138-83: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:52:11Z" - latency: 1.982694ms message: 'network-check-target-ip-10-0-138-83: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:51:11Z" - latency: 1.972454ms message: 'network-check-target-ip-10-0-138-83: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:50:11Z" - latency: 1.611491ms message: 'network-check-target-ip-10-0-138-83: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:49:11Z" - latency: 1.962697ms message: 'network-check-target-ip-10-0-138-83: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:48:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T08:47:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-194-to-network-check-target-ip-10-0-143-193 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-194.ec2.internal uid: 5164a00c-69bc-497c-a003-8c70b732b053 resourceVersion: "15031" uid: 0e8a5e64-bbf3-4852-abb5-97ff3a7d5906 spec: sourcePod: network-check-source-6f8b768455-rzdfq targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-17T08:54:11Z" message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.857516ms message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:54:11Z" - latency: 2.099352ms message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:53:11Z" - latency: 2.074842ms message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:52:11Z" - latency: 1.753537ms message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:51:11Z" - latency: 2.058311ms message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:50:11Z" - latency: 2.1287ms message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:49:11Z" - latency: 2.04571ms message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:48:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T08:47:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-194-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-194.ec2.internal uid: 5164a00c-69bc-497c-a003-8c70b732b053 resourceVersion: "14524" uid: 37ae8ac2-864f-42fa-bb1c-333a6ca14972 spec: sourcePod: network-check-source-6f8b768455-rzdfq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-17T08:53:11Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 828.152µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:53:11Z" - latency: 1.588955ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T08:53:11Z" - latency: 928.032µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:52:11Z" - latency: 1.933364ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T08:52:11Z" - latency: 1.001224ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:51:11Z" - latency: 1.635875ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T08:51:11Z" - latency: 1.010511ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:50:11Z" - latency: 1.904255ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T08:50:11Z" - latency: 864.189µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T08:49:11Z" - latency: 1.890228ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T08:49:11Z" kind: List metadata: resourceVersion: ""