apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T03:22:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-76-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-76.ec2.internal uid: 6f0fe71b-ca2e-49b6-95c0-19ba15c61a78 resourceVersion: "43880" uid: 0003a36c-9a3a-4f86-bd58-d7e38ed6f040 spec: sourcePod: network-check-source-7f44b6dd87-p455n targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-21T03:29:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 874.018µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:50:59Z" - latency: 1.253019ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:49:59Z" - latency: 1.307624ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:48:59Z" - latency: 876.382µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:47:59Z" - latency: 987.596µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:46:59Z" - latency: 837.351µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:45:59Z" - latency: 1.038499ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:44:59Z" - latency: 1.020747ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:43:59Z" - latency: 865.558µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:42:59Z" - latency: 1.252603ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:41:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T03:22:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-76-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-76.ec2.internal uid: 6f0fe71b-ca2e-49b6-95c0-19ba15c61a78 resourceVersion: "46221" uid: 35d893e4-2ec2-4839-852e-aa0e1fbbc3bd spec: sourcePod: network-check-source-7f44b6dd87-p455n targetEndpoint: a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T03:28:59Z" message: 'load-balancer-api-external: tcp connection to a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.587289ms message: 'load-balancer-api-external: tcp connection to a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:52:59Z" - latency: 6.158979ms message: 'load-balancer-api-external: resolved host name a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T03:52:59Z" - latency: 4.333157ms message: 'load-balancer-api-external: tcp connection to a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:51:59Z" - latency: 5.959287ms message: 'load-balancer-api-external: resolved host name a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T03:51:59Z" - latency: 5.048288ms message: 'load-balancer-api-external: tcp connection to a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:50:59Z" - latency: 6.652818ms message: 'load-balancer-api-external: resolved host name a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T03:50:59Z" - latency: 3.379094ms message: 'load-balancer-api-external: tcp connection to a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:49:59Z" - latency: 6.828098ms message: 'load-balancer-api-external: resolved host name a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T03:49:59Z" - latency: 5.679741ms message: 'load-balancer-api-external: tcp connection to a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:48:59Z" - latency: 6.536152ms message: 'load-balancer-api-external: resolved host name a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T03:48:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T03:22:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-76-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-76.ec2.internal uid: 6f0fe71b-ca2e-49b6-95c0-19ba15c61a78 resourceVersion: "46220" uid: 0ceaa1b1-906d-4144-9f4a-819706326bcd spec: sourcePod: network-check-source-7f44b6dd87-p455n targetEndpoint: a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T03:28:59Z" message: 'load-balancer-api-internal: tcp connection to a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.414941ms message: 'load-balancer-api-internal: tcp connection to a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:52:59Z" - latency: 6.070616ms message: 'load-balancer-api-internal: resolved host name a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T03:52:59Z" - latency: 4.153979ms message: 'load-balancer-api-internal: tcp connection to a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:51:59Z" - latency: 5.914346ms message: 'load-balancer-api-internal: resolved host name a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T03:51:59Z" - latency: 4.233376ms message: 'load-balancer-api-internal: tcp connection to a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:50:59Z" - latency: 6.568924ms message: 'load-balancer-api-internal: resolved host name a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T03:50:59Z" - latency: 4.59296ms message: 'load-balancer-api-internal: tcp connection to a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:49:59Z" - latency: 6.750831ms message: 'load-balancer-api-internal: resolved host name a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T03:49:59Z" - latency: 5.685803ms message: 'load-balancer-api-internal: tcp connection to a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:48:59Z" - latency: 6.375401ms message: 'load-balancer-api-internal: resolved host name a375d966ea08b44edb131dc8f6236b42-02d885513df8059b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T03:48:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T03:22:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-76-to-network-check-target-ip-10-0-128-161 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-76.ec2.internal uid: 6f0fe71b-ca2e-49b6-95c0-19ba15c61a78 resourceVersion: "43879" uid: b236c130-f299-4979-8562-f6f5b0dc6a71 spec: sourcePod: network-check-source-7f44b6dd87-p455n targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-21T03:29:59Z" message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.192408ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:50:59Z" - latency: 2.108597ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:49:59Z" - latency: 1.797295ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:48:59Z" - latency: 1.930962ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:47:59Z" - latency: 2.171993ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:46:59Z" - latency: 1.942332ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:45:59Z" - latency: 2.425275ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:44:59Z" - latency: 2.188975ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:43:59Z" - latency: 2.042837ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:42:59Z" - latency: 2.195664ms message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:41:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T03:22:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-76-to-network-check-target-ip-10-0-131-76 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-76.ec2.internal uid: 6f0fe71b-ca2e-49b6-95c0-19ba15c61a78 resourceVersion: "43877" uid: e67d0495-19af-4164-8e8f-7dded4c97a0f spec: sourcePod: network-check-source-7f44b6dd87-p455n targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-21T03:29:59Z" message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 954.379µs message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:50:59Z" - latency: 769.997µs message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:49:59Z" - latency: 1.17938ms message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:48:59Z" - latency: 1.315558ms message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:47:59Z" - latency: 1.060009ms message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:46:59Z" - latency: 828.087µs message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:45:59Z" - latency: 1.08728ms message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:44:59Z" - latency: 990.396µs message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:43:59Z" - latency: 947.532µs message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:42:59Z" - latency: 985.163µs message: 'network-check-target-ip-10-0-131-76: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:41:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T03:22:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-76-to-network-check-target-ip-10-0-137-251 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-76.ec2.internal uid: 6f0fe71b-ca2e-49b6-95c0-19ba15c61a78 resourceVersion: "43878" uid: 4f993acd-a1af-445f-b46d-95ae3632aa60 spec: sourcePod: network-check-source-7f44b6dd87-p455n targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-21T03:29:59Z" message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.292637ms message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:50:59Z" - latency: 2.427964ms message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:49:59Z" - latency: 2.564934ms message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:48:59Z" - latency: 2.374337ms message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:47:59Z" - latency: 2.051336ms message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:46:59Z" - latency: 2.069378ms message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:45:59Z" - latency: 2.234685ms message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:44:59Z" - latency: 2.094699ms message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:43:59Z" - latency: 2.235338ms message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:42:59Z" - latency: 2.172233ms message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:41:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T03:22:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-76-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-76.ec2.internal uid: 6f0fe71b-ca2e-49b6-95c0-19ba15c61a78 resourceVersion: "46219" uid: 5bd04b73-c779-4d2e-9499-4a100a0717ab spec: sourcePod: network-check-source-7f44b6dd87-p455n targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-21T03:28:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 880.04µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:52:59Z" - latency: 1.637832ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T03:52:59Z" - latency: 1.099263ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:51:59Z" - latency: 1.679388ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T03:51:59Z" - latency: 841.6µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:50:59Z" - latency: 1.911258ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T03:50:59Z" - latency: 1.28794ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:49:59Z" - latency: 1.932378ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T03:49:59Z" - latency: 898.728µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T03:48:59Z" - latency: 1.834622ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T03:48:59Z" kind: List metadata: resourceVersion: ""