apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:21:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-16-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-16.ec2.internal uid: 8c6413e7-ce76-4b32-aaaf-b40c56013cf0 resourceVersion: "55338" uid: ff5e43f8-c0a5-4c13-8e26-3809558837b8 spec: sourcePod: network-check-source-989f8b8dc-zgtv7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T02:28:50Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.054004ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:56:50Z" - latency: 1.079128ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:55:50Z" - latency: 926.157µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:54:50Z" - latency: 1.540483ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:53:50Z" - latency: 1.170085ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:52:50Z" - latency: 937.365µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:51:50Z" - latency: 1.060154ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:50:50Z" - latency: 1.074913ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:49:50Z" - latency: 1.401901ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:48:50Z" - latency: 844.532µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:47:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:21:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-16-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-16.ec2.internal uid: 8c6413e7-ce76-4b32-aaaf-b40c56013cf0 resourceVersion: "56379" uid: 39e3f72b-c371-47fc-bc0f-adfa81a2e687 spec: sourcePod: network-check-source-989f8b8dc-zgtv7 targetEndpoint: a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T02:27:50Z" message: 'load-balancer-api-external: tcp connection to a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.60964ms message: 'load-balancer-api-external: tcp connection to a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:57:50Z" - latency: 7.500047ms message: 'load-balancer-api-external: resolved host name a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:57:50Z" - latency: 4.200406ms message: 'load-balancer-api-external: tcp connection to a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:56:50Z" - latency: 6.707824ms message: 'load-balancer-api-external: resolved host name a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:56:50Z" - latency: 4.995569ms message: 'load-balancer-api-external: tcp connection to a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:55:50Z" - latency: 6.77579ms message: 'load-balancer-api-external: resolved host name a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:55:50Z" - latency: 4.511998ms message: 'load-balancer-api-external: tcp connection to a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:54:50Z" - latency: 6.585672ms message: 'load-balancer-api-external: resolved host name a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:54:50Z" - latency: 4.486113ms message: 'load-balancer-api-external: tcp connection to a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:53:50Z" - latency: 7.079155ms message: 'load-balancer-api-external: resolved host name a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:53:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:21:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-16-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-16.ec2.internal uid: 8c6413e7-ce76-4b32-aaaf-b40c56013cf0 resourceVersion: "56380" uid: aa428185-89df-4b98-aa93-0b222a50c12e spec: sourcePod: network-check-source-989f8b8dc-zgtv7 targetEndpoint: a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T02:27:50Z" message: 'load-balancer-api-internal: tcp connection to a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.725979ms message: 'load-balancer-api-internal: tcp connection to a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:57:50Z" - latency: 7.585745ms message: 'load-balancer-api-internal: resolved host name a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:57:50Z" - latency: 4.351921ms message: 'load-balancer-api-internal: tcp connection to a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:56:50Z" - latency: 6.892068ms message: 'load-balancer-api-internal: resolved host name a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:56:50Z" - latency: 5.015178ms message: 'load-balancer-api-internal: tcp connection to a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:55:50Z" - latency: 6.714841ms message: 'load-balancer-api-internal: resolved host name a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:55:50Z" - latency: 4.26209ms message: 'load-balancer-api-internal: tcp connection to a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:54:50Z" - latency: 6.674867ms message: 'load-balancer-api-internal: resolved host name a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:54:50Z" - latency: 4.469311ms message: 'load-balancer-api-internal: tcp connection to a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:53:50Z" - latency: 7.17138ms message: 'load-balancer-api-internal: resolved host name a974046c57ab749449d143314ecae6cb-4696aa4ed0d7f820.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:53:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:21:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-16-to-network-check-target-ip-10-0-133-186 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-16.ec2.internal uid: 8c6413e7-ce76-4b32-aaaf-b40c56013cf0 resourceVersion: "55337" uid: fa0ced58-9f03-49c2-84ab-e20c397f4590 spec: sourcePod: network-check-source-989f8b8dc-zgtv7 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T02:28:50Z" message: 'network-check-target-ip-10-0-133-186: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.630803ms message: 'network-check-target-ip-10-0-133-186: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:56:50Z" - latency: 2.170959ms message: 'network-check-target-ip-10-0-133-186: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:55:50Z" - latency: 2.17498ms message: 'network-check-target-ip-10-0-133-186: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:54:50Z" - latency: 2.522943ms message: 'network-check-target-ip-10-0-133-186: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:53:50Z" - latency: 2.440906ms message: 'network-check-target-ip-10-0-133-186: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:52:50Z" - latency: 2.374578ms message: 'network-check-target-ip-10-0-133-186: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:51:50Z" - latency: 2.492816ms message: 'network-check-target-ip-10-0-133-186: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:50:50Z" - latency: 2.421708ms message: 'network-check-target-ip-10-0-133-186: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:49:50Z" - latency: 2.369922ms message: 'network-check-target-ip-10-0-133-186: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:48:50Z" - latency: 2.304996ms message: 'network-check-target-ip-10-0-133-186: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:47:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:21:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-16-to-network-check-target-ip-10-0-137-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-16.ec2.internal uid: 8c6413e7-ce76-4b32-aaaf-b40c56013cf0 resourceVersion: "55335" uid: 5df9115a-9972-493b-8f86-5499658a7d5f spec: sourcePod: network-check-source-989f8b8dc-zgtv7 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T02:28:50Z" message: 'network-check-target-ip-10-0-137-16: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.013165ms message: 'network-check-target-ip-10-0-137-16: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:56:50Z" - latency: 957.824µs message: 'network-check-target-ip-10-0-137-16: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:55:50Z" - latency: 932.274µs message: 'network-check-target-ip-10-0-137-16: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:54:50Z" - latency: 1.076465ms message: 'network-check-target-ip-10-0-137-16: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:53:50Z" - latency: 1.494594ms message: 'network-check-target-ip-10-0-137-16: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:52:50Z" - latency: 907.806µs message: 'network-check-target-ip-10-0-137-16: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:51:50Z" - latency: 1.466124ms message: 'network-check-target-ip-10-0-137-16: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:50:50Z" - latency: 927.641µs message: 'network-check-target-ip-10-0-137-16: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:49:50Z" - latency: 1.37573ms message: 'network-check-target-ip-10-0-137-16: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:48:50Z" - latency: 915.355µs message: 'network-check-target-ip-10-0-137-16: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:47:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:21:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-16-to-network-check-target-ip-10-0-142-72 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-16.ec2.internal uid: 8c6413e7-ce76-4b32-aaaf-b40c56013cf0 resourceVersion: "55336" uid: 59ac650d-9ec4-4834-a86f-3c97583f1e3f spec: sourcePod: network-check-source-989f8b8dc-zgtv7 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T02:28:50Z" message: 'network-check-target-ip-10-0-142-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.463931ms message: 'network-check-target-ip-10-0-142-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:56:50Z" - latency: 2.40363ms message: 'network-check-target-ip-10-0-142-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:55:50Z" - latency: 2.222036ms message: 'network-check-target-ip-10-0-142-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:54:50Z" - latency: 2.372131ms message: 'network-check-target-ip-10-0-142-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:53:50Z" - latency: 2.500113ms message: 'network-check-target-ip-10-0-142-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:52:50Z" - latency: 2.545629ms message: 'network-check-target-ip-10-0-142-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:51:50Z" - latency: 2.352876ms message: 'network-check-target-ip-10-0-142-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:50:50Z" - latency: 2.34944ms message: 'network-check-target-ip-10-0-142-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:49:50Z" - latency: 2.964359ms message: 'network-check-target-ip-10-0-142-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:48:50Z" - latency: 2.418109ms message: 'network-check-target-ip-10-0-142-72: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:47:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:21:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-16-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-16.ec2.internal uid: 8c6413e7-ce76-4b32-aaaf-b40c56013cf0 resourceVersion: "56378" uid: 6fe5eda0-d34d-4f3f-9f3c-a7314a1931f2 spec: sourcePod: network-check-source-989f8b8dc-zgtv7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T02:27:50Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 931.161µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:57:50Z" - latency: 1.886893ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T02:57:50Z" - latency: 901.607µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:56:50Z" - latency: 1.890836ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T02:56:50Z" - latency: 904.124µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:55:50Z" - latency: 1.650806ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T02:55:50Z" - latency: 922.214µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:54:50Z" - latency: 1.715283ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T02:54:50Z" - latency: 1.002585ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:53:50Z" - latency: 1.844999ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T02:53:50Z" kind: List metadata: resourceVersion: ""