apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T19:50:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-13-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-13.us-west-2.compute.internal uid: 98140ef5-6ef5-4ac9-ae54-87b9d0dd24b3 resourceVersion: "170973" uid: 696fc744-a4f0-4407-8e50-48dae3e13493 spec: sourcePod: network-check-source-6f78d59f99-95m8f targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T19:57:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.181398ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:42:29Z" - latency: 1.045372ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:41:29Z" - latency: 1.341883ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:40:29Z" - latency: 1.277529ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:39:29Z" - latency: 1.075217ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:38:29Z" - latency: 1.255565ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:37:29Z" - latency: 1.128485ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:36:29Z" - latency: 1.148349ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:35:29Z" - latency: 1.002555ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:34:29Z" - latency: 1.064411ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:33:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T19:50:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-13-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-13.us-west-2.compute.internal uid: 98140ef5-6ef5-4ac9-ae54-87b9d0dd24b3 resourceVersion: "172480" uid: 8c58cbdc-1902-4497-8921-ef2144124fdc spec: sourcePod: network-check-source-6f78d59f99-95m8f targetEndpoint: a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T19:56:29Z" message: 'load-balancer-api-external: tcp connection to a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 56.300784ms message: 'load-balancer-api-external: tcp connection to a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:44:29Z" - latency: 7.530867ms message: 'load-balancer-api-external: resolved host name a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T21:44:29Z" - latency: 51.158411ms message: 'load-balancer-api-external: tcp connection to a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:43:29Z" - latency: 6.167963ms message: 'load-balancer-api-external: resolved host name a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T21:43:29Z" - latency: 51.006516ms message: 'load-balancer-api-external: tcp connection to a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:42:29Z" - latency: 7.483969ms message: 'load-balancer-api-external: resolved host name a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T21:42:29Z" - latency: 51.022768ms message: 'load-balancer-api-external: tcp connection to a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:41:29Z" - latency: 7.309192ms message: 'load-balancer-api-external: resolved host name a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T21:41:29Z" - latency: 55.346431ms message: 'load-balancer-api-external: tcp connection to a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:40:29Z" - latency: 7.034879ms message: 'load-balancer-api-external: resolved host name a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T21:40:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T19:50:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-13-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-13.us-west-2.compute.internal uid: 98140ef5-6ef5-4ac9-ae54-87b9d0dd24b3 resourceVersion: "172478" uid: 4c88cf0f-df4f-4365-a01e-2d72f4772e14 spec: sourcePod: network-check-source-6f78d59f99-95m8f targetEndpoint: a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T19:56:29Z" message: 'load-balancer-api-internal: tcp connection to a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 52.230243ms message: 'load-balancer-api-internal: tcp connection to a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:44:29Z" - latency: 7.552741ms message: 'load-balancer-api-internal: resolved host name a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T21:44:29Z" - latency: 51.142034ms message: 'load-balancer-api-internal: tcp connection to a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:43:29Z" - latency: 6.255035ms message: 'load-balancer-api-internal: resolved host name a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T21:43:29Z" - latency: 53.469616ms message: 'load-balancer-api-internal: tcp connection to a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:42:29Z" - latency: 7.556606ms message: 'load-balancer-api-internal: resolved host name a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T21:42:29Z" - latency: 50.674244ms message: 'load-balancer-api-internal: tcp connection to a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:41:29Z" - latency: 7.378977ms message: 'load-balancer-api-internal: resolved host name a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T21:41:29Z" - latency: 56.251639ms message: 'load-balancer-api-internal: tcp connection to a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:40:29Z" - latency: 7.107964ms message: 'load-balancer-api-internal: resolved host name a494c12af1f134ca494febab804ea946-87fdf5767f91ce37.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T21:40:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T19:50:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-13-to-network-check-target-ip-10-0-128-34 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-13.us-west-2.compute.internal uid: 98140ef5-6ef5-4ac9-ae54-87b9d0dd24b3 resourceVersion: "170972" uid: d3a8cfed-cc81-4e21-9342-55faaf27528f spec: sourcePod: network-check-source-6f78d59f99-95m8f targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T19:57:29Z" message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.094222ms message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:42:29Z" - latency: 2.104252ms message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:41:29Z" - latency: 2.485509ms message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:40:29Z" - latency: 2.290518ms message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:39:29Z" - latency: 2.177846ms message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:38:29Z" - latency: 2.335152ms message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:37:29Z" - latency: 2.685808ms message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:36:29Z" - latency: 2.524397ms message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:35:29Z" - latency: 2.08711ms message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:34:29Z" - latency: 2.382716ms message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:33:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T19:50:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-13-to-network-check-target-ip-10-0-134-13 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-13.us-west-2.compute.internal uid: 98140ef5-6ef5-4ac9-ae54-87b9d0dd24b3 resourceVersion: "170971" uid: 48797cce-e8a3-4507-8f1d-dd81adf69f4a spec: sourcePod: network-check-source-6f78d59f99-95m8f targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T19:57:29Z" message: 'network-check-target-ip-10-0-134-13: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.050793ms message: 'network-check-target-ip-10-0-134-13: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:42:29Z" - latency: 1.11712ms message: 'network-check-target-ip-10-0-134-13: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:41:29Z" - latency: 1.29319ms message: 'network-check-target-ip-10-0-134-13: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:40:29Z" - latency: 1.624197ms message: 'network-check-target-ip-10-0-134-13: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:39:29Z" - latency: 867.785µs message: 'network-check-target-ip-10-0-134-13: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:38:29Z" - latency: 1.499117ms message: 'network-check-target-ip-10-0-134-13: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:37:29Z" - latency: 1.39126ms message: 'network-check-target-ip-10-0-134-13: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:36:29Z" - latency: 1.544367ms message: 'network-check-target-ip-10-0-134-13: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:35:29Z" - latency: 1.271343ms message: 'network-check-target-ip-10-0-134-13: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:34:29Z" - latency: 1.1606ms message: 'network-check-target-ip-10-0-134-13: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:33:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T19:50:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-13-to-network-check-target-ip-10-0-134-196 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-13.us-west-2.compute.internal uid: 98140ef5-6ef5-4ac9-ae54-87b9d0dd24b3 resourceVersion: "170970" uid: 0e90febc-7240-4834-9349-25ea96398fcc spec: sourcePod: network-check-source-6f78d59f99-95m8f targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T19:57:29Z" message: 'network-check-target-ip-10-0-134-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.938601ms message: 'network-check-target-ip-10-0-134-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:42:29Z" - latency: 1.946499ms message: 'network-check-target-ip-10-0-134-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:41:29Z" - latency: 2.089094ms message: 'network-check-target-ip-10-0-134-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:40:29Z" - latency: 1.973312ms message: 'network-check-target-ip-10-0-134-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:39:29Z" - latency: 1.937625ms message: 'network-check-target-ip-10-0-134-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:38:29Z" - latency: 2.173699ms message: 'network-check-target-ip-10-0-134-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:37:29Z" - latency: 2.020544ms message: 'network-check-target-ip-10-0-134-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:36:29Z" - latency: 1.854336ms message: 'network-check-target-ip-10-0-134-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:35:29Z" - latency: 1.891562ms message: 'network-check-target-ip-10-0-134-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:34:29Z" - latency: 2.009529ms message: 'network-check-target-ip-10-0-134-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:33:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T19:50:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-13-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-13.us-west-2.compute.internal uid: 98140ef5-6ef5-4ac9-ae54-87b9d0dd24b3 resourceVersion: "172477" uid: 289fd021-bdbe-4a77-ad64-480e21403b16 spec: sourcePod: network-check-source-6f78d59f99-95m8f targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T19:56:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 844.653µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:44:29Z" - latency: 624.332µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T21:44:29Z" - latency: 1.003852ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:43:29Z" - latency: 598.895µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T21:43:29Z" - latency: 922.358µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:42:29Z" - latency: 602.058µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T21:42:29Z" - latency: 788.207µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:41:29Z" - latency: 536.208µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T21:41:29Z" - latency: 810.152µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T21:40:29Z" - latency: 573.093µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T21:40:29Z" kind: List metadata: resourceVersion: ""