apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T21:05:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-35-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-35.ec2.internal uid: 52e118ea-5c9d-4735-ab87-0f960ae1014b resourceVersion: "46329" uid: 0ceaf7f6-b0f1-4b2a-9147-a5810b45012a spec: sourcePod: network-check-source-dbd9cf844-cjf74 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-05T21:12:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 774.879µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:33:58Z" - latency: 947.996µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:32:58Z" - latency: 1.119104ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:31:58Z" - latency: 1.186887ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:30:58Z" - latency: 1.225466ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:29:58Z" - latency: 1.010112ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:28:58Z" - latency: 1.086723ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:27:58Z" - latency: 1.222579ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:26:58Z" - latency: 1.04408ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:25:58Z" - latency: 1.020658ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:24:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T21:05:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-35-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-35.ec2.internal uid: 52e118ea-5c9d-4735-ab87-0f960ae1014b resourceVersion: "48365" uid: a4f1c862-5b61-4b4e-a7a4-bf13aa29b248 spec: sourcePod: network-check-source-dbd9cf844-cjf74 targetEndpoint: a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T21:11:58Z" message: 'load-balancer-api-external: tcp connection to a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.722381ms message: 'load-balancer-api-external: tcp connection to a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:35:58Z" - latency: 9.28116ms message: 'load-balancer-api-external: resolved host name a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T21:35:58Z" - latency: 3.112465ms message: 'load-balancer-api-external: tcp connection to a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:34:58Z" - latency: 7.993137ms message: 'load-balancer-api-external: resolved host name a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T21:34:58Z" - latency: 4.610074ms message: 'load-balancer-api-external: tcp connection to a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:33:58Z" - latency: 9.493327ms message: 'load-balancer-api-external: resolved host name a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T21:33:58Z" - latency: 4.427096ms message: 'load-balancer-api-external: tcp connection to a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:32:58Z" - latency: 8.517251ms message: 'load-balancer-api-external: resolved host name a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T21:32:58Z" - latency: 4.031694ms message: 'load-balancer-api-external: tcp connection to a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:31:58Z" - latency: 8.158574ms message: 'load-balancer-api-external: resolved host name a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T21:31:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T21:05:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-35-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-35.ec2.internal uid: 52e118ea-5c9d-4735-ab87-0f960ae1014b resourceVersion: "48364" uid: e63f8667-8632-4ea9-a0e2-d9d70f461437 spec: sourcePod: network-check-source-dbd9cf844-cjf74 targetEndpoint: a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T21:11:58Z" message: 'load-balancer-api-internal: tcp connection to a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.142081ms message: 'load-balancer-api-internal: tcp connection to a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:35:58Z" - latency: 9.272109ms message: 'load-balancer-api-internal: resolved host name a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T21:35:58Z" - latency: 3.122102ms message: 'load-balancer-api-internal: tcp connection to a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:34:58Z" - latency: 7.939769ms message: 'load-balancer-api-internal: resolved host name a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T21:34:58Z" - latency: 4.603578ms message: 'load-balancer-api-internal: tcp connection to a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:33:58Z" - latency: 8.691636ms message: 'load-balancer-api-internal: resolved host name a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T21:33:58Z" - latency: 4.341979ms message: 'load-balancer-api-internal: tcp connection to a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:32:58Z" - latency: 8.550491ms message: 'load-balancer-api-internal: resolved host name a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T21:32:58Z" - latency: 3.939025ms message: 'load-balancer-api-internal: tcp connection to a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:31:58Z" - latency: 8.052418ms message: 'load-balancer-api-internal: resolved host name a0eb3b7c1ce304ca4947343cd1933f41-01e8cf7ca1075fec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T21:31:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T21:05:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-35-to-network-check-target-ip-10-0-133-35 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-35.ec2.internal uid: 52e118ea-5c9d-4735-ab87-0f960ae1014b resourceVersion: "46325" uid: 17eee739-a3ec-4c9d-95de-f343cef08b14 spec: sourcePod: network-check-source-dbd9cf844-cjf74 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-05T21:12:58Z" message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.287218ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:33:58Z" - latency: 894.512µs message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:32:58Z" - latency: 873.127µs message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:31:58Z" - latency: 955.27µs message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:30:58Z" - latency: 806.029µs message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:29:58Z" - latency: 1.31866ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:28:58Z" - latency: 924.131µs message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:27:58Z" - latency: 1.050236ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:26:58Z" - latency: 855.96µs message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:25:58Z" - latency: 1.17911ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:24:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T21:05:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-35-to-network-check-target-ip-10-0-138-251 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-35.ec2.internal uid: 52e118ea-5c9d-4735-ab87-0f960ae1014b resourceVersion: "46328" uid: 36d9c4c4-d9b9-40c9-91c0-7d0a91d85a4a spec: sourcePod: network-check-source-dbd9cf844-cjf74 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-05T21:12:58Z" message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.391526ms message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:33:58Z" - latency: 2.164443ms message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:32:58Z" - latency: 2.257655ms message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:31:58Z" - latency: 1.84522ms message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:30:58Z" - latency: 2.322182ms message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:29:58Z" - latency: 2.597082ms message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:28:58Z" - latency: 2.214933ms message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:27:58Z" - latency: 2.37398ms message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:26:58Z" - latency: 2.248ms message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:25:58Z" - latency: 2.41402ms message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:24:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T21:05:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-35-to-network-check-target-ip-10-0-140-154 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-35.ec2.internal uid: 52e118ea-5c9d-4735-ab87-0f960ae1014b resourceVersion: "46326" uid: c0d74d04-fa5a-481a-9acd-215e1921f4d4 spec: sourcePod: network-check-source-dbd9cf844-cjf74 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-05T21:12:58Z" message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.912981ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:33:58Z" - latency: 2.541146ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:32:58Z" - latency: 2.316065ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:31:58Z" - latency: 2.211346ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:30:58Z" - latency: 2.625643ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:29:58Z" - latency: 2.212382ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:28:58Z" - latency: 2.588663ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:27:58Z" - latency: 2.383768ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:26:58Z" - latency: 2.255758ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:25:58Z" - latency: 2.471706ms message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:24:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T21:05:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-35-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-35.ec2.internal uid: 52e118ea-5c9d-4735-ab87-0f960ae1014b resourceVersion: "48363" uid: 75b10318-b381-4ede-a17f-f5f1ffb085f9 spec: sourcePod: network-check-source-dbd9cf844-cjf74 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-05T21:11:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.009435ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:35:58Z" - latency: 2.287086ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T21:35:58Z" - latency: 884.912µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:34:58Z" - latency: 1.657963ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T21:34:58Z" - latency: 883.869µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:33:58Z" - latency: 1.080833ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T21:33:58Z" - latency: 1.270395ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:32:58Z" - latency: 2.243551ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T21:32:58Z" - latency: 1.334107ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T21:31:58Z" - latency: 1.690798ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T21:31:58Z" kind: List metadata: resourceVersion: ""