apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:48:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-161-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-161.ec2.internal uid: 5dd45c59-7daa-4531-9bd9-d2d84cad2f30 resourceVersion: "88277" uid: 8652dfa1-0f06-4312-9736-f107e03442b6 spec: sourcePod: network-check-source-6f8b768455-48rtn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-16T18:55:24Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.192291ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:58:24Z" - latency: 882.71µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:57:24Z" - latency: 1.43919ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:56:24Z" - latency: 1.285221ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:55:24Z" - latency: 1.390777ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:54:24Z" - latency: 1.038451ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:53:24Z" - latency: 861.561µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:52:24Z" - latency: 1.155623ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:51:24Z" - latency: 1.045708ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:50:24Z" - latency: 1.510587ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:49:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:48:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-161-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-161.ec2.internal uid: 5dd45c59-7daa-4531-9bd9-d2d84cad2f30 resourceVersion: "89840" uid: 612194f9-ea77-4592-9c1d-f1e9aa77f995 spec: sourcePod: network-check-source-6f8b768455-48rtn targetEndpoint: a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-16T18:54:24Z" message: 'load-balancer-api-external: tcp connection to a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.636661ms message: 'load-balancer-api-external: tcp connection to a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T20:00:24Z" - latency: 8.222252ms message: 'load-balancer-api-external: resolved host name a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T20:00:24Z" - latency: 6.288793ms message: 'load-balancer-api-external: tcp connection to a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:59:24Z" - latency: 8.526147ms message: 'load-balancer-api-external: resolved host name a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:59:24Z" - latency: 4.301157ms message: 'load-balancer-api-external: tcp connection to a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:58:24Z" - latency: 8.907122ms message: 'load-balancer-api-external: resolved host name a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:58:24Z" - latency: 4.089418ms message: 'load-balancer-api-external: tcp connection to a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:57:24Z" - latency: 9.636314ms message: 'load-balancer-api-external: resolved host name a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:57:24Z" - latency: 6.38004ms message: 'load-balancer-api-external: tcp connection to a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:56:24Z" - latency: 9.398691ms message: 'load-balancer-api-external: resolved host name a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:56:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:48:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-161-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-161.ec2.internal uid: 5dd45c59-7daa-4531-9bd9-d2d84cad2f30 resourceVersion: "89839" uid: 1d1895ae-8aa9-48f5-9604-754ab9df4303 spec: sourcePod: network-check-source-6f8b768455-48rtn targetEndpoint: a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-16T18:54:24Z" message: 'load-balancer-api-internal: tcp connection to a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.019984ms message: 'load-balancer-api-internal: tcp connection to a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T20:00:24Z" - latency: 8.165611ms message: 'load-balancer-api-internal: resolved host name a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T20:00:24Z" - latency: 6.051437ms message: 'load-balancer-api-internal: tcp connection to a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:59:24Z" - latency: 8.569238ms message: 'load-balancer-api-internal: resolved host name a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:59:24Z" - latency: 4.310989ms message: 'load-balancer-api-internal: tcp connection to a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:58:24Z" - latency: 8.940876ms message: 'load-balancer-api-internal: resolved host name a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:58:24Z" - latency: 4.381695ms message: 'load-balancer-api-internal: tcp connection to a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:57:24Z" - latency: 9.455362ms message: 'load-balancer-api-internal: resolved host name a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:57:24Z" - latency: 6.550349ms message: 'load-balancer-api-internal: tcp connection to a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:56:24Z" - latency: 9.344977ms message: 'load-balancer-api-internal: resolved host name a9911315785324c36b509f63401684a4-e77f66e0862d2d51.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T19:56:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:48:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-161-to-network-check-target-ip-10-0-129-125 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-161.ec2.internal uid: 5dd45c59-7daa-4531-9bd9-d2d84cad2f30 resourceVersion: "88276" uid: 84b783a9-d49a-4608-9678-73b64193413f spec: sourcePod: network-check-source-6f8b768455-48rtn targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-16T18:55:24Z" message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.064558ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:58:24Z" - latency: 2.255555ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:57:24Z" - latency: 2.393338ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:56:24Z" - latency: 2.384129ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:55:24Z" - latency: 2.55088ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:54:24Z" - latency: 2.746407ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:53:24Z" - latency: 2.489864ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:52:24Z" - latency: 2.710778ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:51:24Z" - latency: 2.571242ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:50:24Z" - latency: 3.082741ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:49:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:48:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-161-to-network-check-target-ip-10-0-135-244 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-161.ec2.internal uid: 5dd45c59-7daa-4531-9bd9-d2d84cad2f30 resourceVersion: "88274" uid: 9f7da670-45ca-4e4e-92f8-26f707d2c14a spec: sourcePod: network-check-source-6f8b768455-48rtn targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-16T18:55:24Z" message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.368792ms message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:58:24Z" - latency: 2.334759ms message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:57:24Z" - latency: 2.65101ms message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:56:24Z" - latency: 2.25183ms message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:55:24Z" - latency: 2.288581ms message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:54:24Z" - latency: 2.308163ms message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:53:24Z" - latency: 2.402374ms message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:52:24Z" - latency: 2.627783ms message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:51:24Z" - latency: 2.117977ms message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:50:24Z" - latency: 2.323062ms message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:49:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:48:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-161-to-network-check-target-ip-10-0-143-161 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-161.ec2.internal uid: 5dd45c59-7daa-4531-9bd9-d2d84cad2f30 resourceVersion: "88275" uid: eedecd5d-72e4-44e7-84d7-2b7c945fca91 spec: sourcePod: network-check-source-6f8b768455-48rtn targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-16T18:55:24Z" message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.8266ms message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:58:24Z" - latency: 1.259334ms message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:57:24Z" - latency: 1.878645ms message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:56:24Z" - latency: 935.646µs message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:55:24Z" - latency: 970.803µs message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:54:24Z" - latency: 1.010471ms message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:53:24Z" - latency: 997.902µs message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:52:24Z" - latency: 1.337075ms message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:51:24Z" - latency: 1.007906ms message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:50:24Z" - latency: 990.236µs message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:49:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T18:48:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-161-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-161.ec2.internal uid: 5dd45c59-7daa-4531-9bd9-d2d84cad2f30 resourceVersion: "89838" uid: 6f5fefaf-8558-4a53-9169-e068b9c313aa spec: sourcePod: network-check-source-6f8b768455-48rtn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-16T18:54:24Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 934.581µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T20:00:24Z" - latency: 1.766888ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T20:00:24Z" - latency: 881.143µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:59:24Z" - latency: 2.115762ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T19:59:24Z" - latency: 916.563µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:58:24Z" - latency: 1.792273ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T19:58:24Z" - latency: 945.686µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:57:24Z" - latency: 1.830679ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T19:57:24Z" - latency: 937.087µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T19:56:24Z" - latency: 2.345928ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T19:56:24Z" kind: List metadata: resourceVersion: ""