apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T21:25:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-99-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-99.ec2.internal uid: ead0bc72-d30b-447d-900b-ca59c7c3f658 resourceVersion: "43532" uid: 2bb15fa4-87a2-4f2c-a1e3-75993d03c2c2 spec: sourcePod: network-check-source-7f44b6dd87-vh5mr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-21T21:32:16Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 983.135µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:53:16Z" - latency: 1.053247ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:52:16Z" - latency: 1.111075ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:51:16Z" - latency: 1.108899ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:50:16Z" - latency: 1.356786ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:49:16Z" - latency: 980.712µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:48:16Z" - latency: 1.380729ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:47:16Z" - latency: 1.177085ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:46:16Z" - latency: 1.30846ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:45:16Z" - latency: 1.200237ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:44:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T21:25:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-99-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-99.ec2.internal uid: ead0bc72-d30b-447d-900b-ca59c7c3f658 resourceVersion: "39281" uid: 2a074df4-b809-4558-99f2-b5bae147715d spec: sourcePod: network-check-source-7f44b6dd87-vh5mr targetEndpoint: a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T21:31:16Z" message: 'load-balancer-api-external: tcp connection to a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.123018ms message: 'load-balancer-api-external: tcp connection to a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:49:16Z" - latency: 6.674008ms message: 'load-balancer-api-external: resolved host name a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T21:49:16Z" - latency: 4.259624ms message: 'load-balancer-api-external: tcp connection to a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:48:16Z" - latency: 6.127481ms message: 'load-balancer-api-external: resolved host name a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T21:48:16Z" - latency: 5.430946ms message: 'load-balancer-api-external: tcp connection to a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:47:16Z" - latency: 10.513011ms message: 'load-balancer-api-external: resolved host name a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T21:47:16Z" - latency: 5.197173ms message: 'load-balancer-api-external: tcp connection to a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:46:16Z" - latency: 6.622042ms message: 'load-balancer-api-external: resolved host name a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T21:46:16Z" - latency: 4.458938ms message: 'load-balancer-api-external: tcp connection to a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:45:16Z" - latency: 6.524597ms message: 'load-balancer-api-external: resolved host name a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T21:45:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T21:25:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-99-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-99.ec2.internal uid: ead0bc72-d30b-447d-900b-ca59c7c3f658 resourceVersion: "39282" uid: cf43ee89-6a68-4315-b1fa-1e5edd493220 spec: sourcePod: network-check-source-7f44b6dd87-vh5mr targetEndpoint: a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T21:31:16Z" message: 'load-balancer-api-internal: tcp connection to a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.17619ms message: 'load-balancer-api-internal: tcp connection to a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:49:16Z" - latency: 6.61609ms message: 'load-balancer-api-internal: resolved host name a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T21:49:16Z" - latency: 4.205517ms message: 'load-balancer-api-internal: tcp connection to a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:48:16Z" - latency: 6.074696ms message: 'load-balancer-api-internal: resolved host name a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T21:48:16Z" - latency: 3.98092ms message: 'load-balancer-api-internal: tcp connection to a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:47:16Z" - latency: 10.465215ms message: 'load-balancer-api-internal: resolved host name a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T21:47:16Z" - latency: 5.360717ms message: 'load-balancer-api-internal: tcp connection to a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:46:16Z" - latency: 6.658171ms message: 'load-balancer-api-internal: resolved host name a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T21:46:16Z" - latency: 4.82105ms message: 'load-balancer-api-internal: tcp connection to a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:45:16Z" - latency: 6.467307ms message: 'load-balancer-api-internal: resolved host name a4ee02ab84887491896bf1d1b86c40f2-eda9fcfabf81eee1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T21:45:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T21:25:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-99-to-network-check-target-ip-10-0-129-28 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-99.ec2.internal uid: ead0bc72-d30b-447d-900b-ca59c7c3f658 resourceVersion: "43535" uid: d5adda45-b3f9-44a6-8410-d4bab631ad3a spec: sourcePod: network-check-source-7f44b6dd87-vh5mr targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T21:32:16Z" message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 577.14µs message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:53:16Z" - latency: 1.868225ms message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:52:16Z" - latency: 2.040669ms message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:51:16Z" - latency: 1.806759ms message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:50:16Z" - latency: 712.939µs message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:49:16Z" - latency: 1.821398ms message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:48:16Z" - latency: 563.146µs message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:47:16Z" - latency: 1.638617ms message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:46:16Z" - latency: 1.539058ms message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:45:16Z" - latency: 578.438µs message: 'network-check-target-ip-10-0-129-28: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:44:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T21:25:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-99-to-network-check-target-ip-10-0-133-99 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-99.ec2.internal uid: ead0bc72-d30b-447d-900b-ca59c7c3f658 resourceVersion: "43533" uid: 7f9a9861-b5c1-442a-b286-f9b64cf86966 spec: sourcePod: network-check-source-7f44b6dd87-vh5mr targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-21T21:32:16Z" message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 576.079µs message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:53:16Z" - latency: 624.998µs message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:52:16Z" - latency: 396.687µs message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:51:16Z" - latency: 555.595µs message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:50:16Z" - latency: 778.434µs message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:49:16Z" - latency: 371.37µs message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:48:16Z" - latency: 590.894µs message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:47:16Z" - latency: 584.297µs message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:46:16Z" - latency: 362.694µs message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:45:16Z" - latency: 537.693µs message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:44:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T21:25:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-99-to-network-check-target-ip-10-0-135-166 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-99.ec2.internal uid: ead0bc72-d30b-447d-900b-ca59c7c3f658 resourceVersion: "43534" uid: c6c60c05-7c46-44a7-a2a5-48ca622ef469 spec: sourcePod: network-check-source-7f44b6dd87-vh5mr targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T21:32:16Z" message: 'network-check-target-ip-10-0-135-166: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.06782ms message: 'network-check-target-ip-10-0-135-166: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:53:16Z" - latency: 701.71µs message: 'network-check-target-ip-10-0-135-166: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:52:16Z" - latency: 4.21118ms message: 'network-check-target-ip-10-0-135-166: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:51:16Z" - latency: 637.819µs message: 'network-check-target-ip-10-0-135-166: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:50:16Z" - latency: 2.154955ms message: 'network-check-target-ip-10-0-135-166: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:49:16Z" - latency: 1.888348ms message: 'network-check-target-ip-10-0-135-166: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:48:16Z" - latency: 1.621257ms message: 'network-check-target-ip-10-0-135-166: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:47:16Z" - latency: 701.252µs message: 'network-check-target-ip-10-0-135-166: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:46:16Z" - latency: 1.924863ms message: 'network-check-target-ip-10-0-135-166: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:45:16Z" - latency: 1.695565ms message: 'network-check-target-ip-10-0-135-166: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:44:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T21:25:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-99-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-99.ec2.internal uid: ead0bc72-d30b-447d-900b-ca59c7c3f658 resourceVersion: "39279" uid: 2756a346-7d17-4949-a773-985576d49351 spec: sourcePod: network-check-source-7f44b6dd87-vh5mr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-21T21:31:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.052848ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:49:16Z" - latency: 1.6764ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T21:49:16Z" - latency: 949.599µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:48:16Z" - latency: 1.604841ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T21:48:16Z" - latency: 2.008693ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:47:16Z" - latency: 1.707246ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T21:47:16Z" - latency: 1.943757ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:46:16Z" - latency: 1.788689ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T21:46:16Z" - latency: 1.025985ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:45:16Z" - latency: 1.951113ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T21:45:16Z" kind: List metadata: resourceVersion: ""