apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T22:27:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-16-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-16.ec2.internal uid: 14cc08ed-8689-43aa-8e23-225359d5d864 resourceVersion: "57436" uid: ee326700-5167-464c-8d98-b3e7d3f6eb5a spec: sourcePod: network-check-source-7bc5b6bf85-jtsls targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-20T22:34:14Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.055421ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:09:14Z" - latency: 1.233859ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:08:14Z" - latency: 1.210427ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:07:14Z" - latency: 1.050125ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:06:14Z" - latency: 943.043µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:05:14Z" - latency: 1.085776ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:04:14Z" - latency: 1.065661ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:03:14Z" - latency: 765.903µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:02:14Z" - latency: 1.117441ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:01:14Z" - latency: 971.414µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:00:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T22:27:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-16-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-16.ec2.internal uid: 14cc08ed-8689-43aa-8e23-225359d5d864 resourceVersion: "57437" uid: 9bc664c2-7da4-42c6-acbf-cc10cc6f4605 spec: sourcePod: network-check-source-7bc5b6bf85-jtsls targetEndpoint: add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T22:33:14Z" message: 'load-balancer-api-external: tcp connection to add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.19597ms message: 'load-balancer-api-external: tcp connection to add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:09:14Z" - latency: 6.106649ms message: 'load-balancer-api-external: resolved host name add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T23:09:14Z" - latency: 4.519298ms message: 'load-balancer-api-external: tcp connection to add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:08:14Z" - latency: 7.402625ms message: 'load-balancer-api-external: resolved host name add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T23:08:14Z" - latency: 3.847073ms message: 'load-balancer-api-external: tcp connection to add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:07:14Z" - latency: 8.453175ms message: 'load-balancer-api-external: resolved host name add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T23:07:14Z" - latency: 5.140469ms message: 'load-balancer-api-external: tcp connection to add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:06:14Z" - latency: 5.983178ms message: 'load-balancer-api-external: resolved host name add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T23:06:14Z" - latency: 4.177452ms message: 'load-balancer-api-external: tcp connection to add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:05:14Z" - latency: 7.169334ms message: 'load-balancer-api-external: resolved host name add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T23:05:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T22:27:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-16-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-16.ec2.internal uid: 14cc08ed-8689-43aa-8e23-225359d5d864 resourceVersion: "57438" uid: d0687b07-9576-4f45-8d82-f61dc91c2eaf spec: sourcePod: network-check-source-7bc5b6bf85-jtsls targetEndpoint: add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T22:33:14Z" message: 'load-balancer-api-internal: tcp connection to add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.225307ms message: 'load-balancer-api-internal: tcp connection to add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:09:14Z" - latency: 6.21325ms message: 'load-balancer-api-internal: resolved host name add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T23:09:14Z" - latency: 4.492863ms message: 'load-balancer-api-internal: tcp connection to add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:08:14Z" - latency: 7.510919ms message: 'load-balancer-api-internal: resolved host name add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T23:08:14Z" - latency: 3.837444ms message: 'load-balancer-api-internal: tcp connection to add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:07:14Z" - latency: 8.533271ms message: 'load-balancer-api-internal: resolved host name add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T23:07:14Z" - latency: 5.149651ms message: 'load-balancer-api-internal: tcp connection to add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:06:14Z" - latency: 6.078156ms message: 'load-balancer-api-internal: resolved host name add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T23:06:14Z" - latency: 3.581289ms message: 'load-balancer-api-internal: tcp connection to add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:05:14Z" - latency: 7.245259ms message: 'load-balancer-api-internal: resolved host name add5f93aa498046fcac9dbe33cf3ad76-ebae02f3507215bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T23:05:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T22:27:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-16-to-network-check-target-ip-10-0-129-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-16.ec2.internal uid: 14cc08ed-8689-43aa-8e23-225359d5d864 resourceVersion: "57432" uid: 3ea57b64-00a6-4195-abfd-5169c7254578 spec: sourcePod: network-check-source-7bc5b6bf85-jtsls targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-20T22:34:14Z" message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 978.988µs message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:09:14Z" - latency: 1.604849ms message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:08:14Z" - latency: 927.81µs message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:07:14Z" - latency: 857.125µs message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:06:14Z" - latency: 1.101222ms message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:05:14Z" - latency: 770.186µs message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:04:14Z" - latency: 846.646µs message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:03:14Z" - latency: 1.306371ms message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:02:14Z" - latency: 1.321163ms message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:01:14Z" - latency: 952.008µs message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:00:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T22:27:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-16-to-network-check-target-ip-10-0-133-74 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-16.ec2.internal uid: 14cc08ed-8689-43aa-8e23-225359d5d864 resourceVersion: "57433" uid: 32477ff4-4285-4f6c-85e0-d68f80037570 spec: sourcePod: network-check-source-7bc5b6bf85-jtsls targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-20T22:34:14Z" message: 'network-check-target-ip-10-0-133-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.558497ms message: 'network-check-target-ip-10-0-133-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:09:14Z" - latency: 2.285161ms message: 'network-check-target-ip-10-0-133-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:08:14Z" - latency: 1.914737ms message: 'network-check-target-ip-10-0-133-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:07:14Z" - latency: 2.391889ms message: 'network-check-target-ip-10-0-133-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:06:14Z" - latency: 2.090652ms message: 'network-check-target-ip-10-0-133-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:05:14Z" - latency: 2.172372ms message: 'network-check-target-ip-10-0-133-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:04:14Z" - latency: 2.530459ms message: 'network-check-target-ip-10-0-133-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:03:14Z" - latency: 2.573359ms message: 'network-check-target-ip-10-0-133-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:02:14Z" - latency: 2.541347ms message: 'network-check-target-ip-10-0-133-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:01:14Z" - latency: 2.367472ms message: 'network-check-target-ip-10-0-133-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:00:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T22:27:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-16-to-network-check-target-ip-10-0-135-161 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-16.ec2.internal uid: 14cc08ed-8689-43aa-8e23-225359d5d864 resourceVersion: "57434" uid: 92c62d79-6348-4a84-9dd0-41b78e47b162 spec: sourcePod: network-check-source-7bc5b6bf85-jtsls targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-20T22:34:14Z" message: 'network-check-target-ip-10-0-135-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.424929ms message: 'network-check-target-ip-10-0-135-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:09:14Z" - latency: 2.444245ms message: 'network-check-target-ip-10-0-135-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:08:14Z" - latency: 2.352677ms message: 'network-check-target-ip-10-0-135-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:07:14Z" - latency: 2.377942ms message: 'network-check-target-ip-10-0-135-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:06:14Z" - latency: 2.447222ms message: 'network-check-target-ip-10-0-135-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:05:14Z" - latency: 2.252056ms message: 'network-check-target-ip-10-0-135-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:04:14Z" - latency: 2.431367ms message: 'network-check-target-ip-10-0-135-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:03:14Z" - latency: 2.343532ms message: 'network-check-target-ip-10-0-135-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:02:14Z" - latency: 2.582432ms message: 'network-check-target-ip-10-0-135-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:01:14Z" - latency: 2.336684ms message: 'network-check-target-ip-10-0-135-161: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:00:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T22:27:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-16-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-16.ec2.internal uid: 14cc08ed-8689-43aa-8e23-225359d5d864 resourceVersion: "57435" uid: 46760d96-aaef-4e7d-98ec-d2d22dfcbb13 spec: sourcePod: network-check-source-7bc5b6bf85-jtsls targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-20T22:33:14Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.07819ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:09:14Z" - latency: 1.835272ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T23:09:14Z" - latency: 885.599µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:08:14Z" - latency: 1.978488ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T23:08:14Z" - latency: 907.576µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:07:14Z" - latency: 1.677344ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T23:07:14Z" - latency: 1.277982ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:06:14Z" - latency: 1.793193ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T23:06:14Z" - latency: 820.349µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T23:05:14Z" - latency: 1.924697ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T23:05:14Z" kind: List metadata: resourceVersion: ""