apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T20:50:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-214-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-214.ec2.internal uid: 73fd6bd5-d3f0-4715-b3e3-f4b65256a672 resourceVersion: "46795" uid: 5dc8abce-5e52-4d88-ac55-b503b97a08af spec: sourcePod: network-check-source-dbd9cf844-m7lkf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-03T20:57:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.280273ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:18:21Z" - latency: 1.053026ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:17:21Z" - latency: 1.356127ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:16:21Z" - latency: 1.48586ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:15:21Z" - latency: 984.364µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:14:21Z" - latency: 1.096734ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:13:21Z" - latency: 978.187µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:12:21Z" - latency: 1.435295ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:11:21Z" - latency: 1.136742ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:10:21Z" - latency: 1.089582ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:09:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T20:50:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-214-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-214.ec2.internal uid: 73fd6bd5-d3f0-4715-b3e3-f4b65256a672 resourceVersion: "48938" uid: e994f6a0-bfd0-4b44-9fbb-4ccac2e2708d spec: sourcePod: network-check-source-dbd9cf844-m7lkf targetEndpoint: a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T20:56:21Z" message: 'load-balancer-api-external: tcp connection to a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.928714ms message: 'load-balancer-api-external: tcp connection to a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:20:21Z" - latency: 8.023365ms message: 'load-balancer-api-external: resolved host name a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T21:20:21Z" - latency: 5.249771ms message: 'load-balancer-api-external: tcp connection to a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:19:21Z" - latency: 8.10314ms message: 'load-balancer-api-external: resolved host name a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T21:19:21Z" - latency: 5.303858ms message: 'load-balancer-api-external: tcp connection to a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:18:21Z" - latency: 7.793079ms message: 'load-balancer-api-external: resolved host name a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T21:18:21Z" - latency: 5.561553ms message: 'load-balancer-api-external: tcp connection to a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:17:21Z" - latency: 8.267328ms message: 'load-balancer-api-external: resolved host name a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T21:17:21Z" - latency: 5.707453ms message: 'load-balancer-api-external: tcp connection to a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:16:21Z" - latency: 9.424315ms message: 'load-balancer-api-external: resolved host name a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T21:16:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T20:50:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-214-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-214.ec2.internal uid: 73fd6bd5-d3f0-4715-b3e3-f4b65256a672 resourceVersion: "48939" uid: d06ce659-7d9c-4393-98f4-0ada143201a4 spec: sourcePod: network-check-source-dbd9cf844-m7lkf targetEndpoint: a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T20:56:21Z" message: 'load-balancer-api-internal: tcp connection to a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.914938ms message: 'load-balancer-api-internal: tcp connection to a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:20:21Z" - latency: 8.062911ms message: 'load-balancer-api-internal: resolved host name a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T21:20:21Z" - latency: 5.444379ms message: 'load-balancer-api-internal: tcp connection to a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:19:21Z" - latency: 8.122696ms message: 'load-balancer-api-internal: resolved host name a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T21:19:21Z" - latency: 3.815ms message: 'load-balancer-api-internal: tcp connection to a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:18:21Z" - latency: 7.846719ms message: 'load-balancer-api-internal: resolved host name a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T21:18:21Z" - latency: 5.551846ms message: 'load-balancer-api-internal: tcp connection to a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:17:21Z" - latency: 8.16954ms message: 'load-balancer-api-internal: resolved host name a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T21:17:21Z" - latency: 5.682379ms message: 'load-balancer-api-internal: tcp connection to a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:16:21Z" - latency: 9.50782ms message: 'load-balancer-api-internal: resolved host name a40c8fe3e2f904dda96a1ede0d3ced0c-8c571b3a02b2e8db.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T21:16:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T20:50:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-214-to-network-check-target-ip-10-0-130-87 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-214.ec2.internal uid: 73fd6bd5-d3f0-4715-b3e3-f4b65256a672 resourceVersion: "46792" uid: d4ac0441-b87c-4491-9bda-452905c538cb spec: sourcePod: network-check-source-dbd9cf844-m7lkf targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-03T20:57:21Z" message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.683914ms message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:18:21Z" - latency: 1.824006ms message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:17:21Z" - latency: 1.930062ms message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:16:21Z" - latency: 2.237711ms message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:15:21Z" - latency: 1.552053ms message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:14:21Z" - latency: 2.06274ms message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:13:21Z" - latency: 1.972507ms message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:12:21Z" - latency: 1.971436ms message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:11:21Z" - latency: 2.029853ms message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:10:21Z" - latency: 1.622547ms message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:09:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T20:50:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-214-to-network-check-target-ip-10-0-139-214 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-214.ec2.internal uid: 73fd6bd5-d3f0-4715-b3e3-f4b65256a672 resourceVersion: "46791" uid: f136a498-ca4f-4d73-9132-695b6baf1924 spec: sourcePod: network-check-source-dbd9cf844-m7lkf targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-03T20:57:21Z" message: 'network-check-target-ip-10-0-139-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 838.437µs message: 'network-check-target-ip-10-0-139-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:18:21Z" - latency: 906.538µs message: 'network-check-target-ip-10-0-139-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:17:21Z" - latency: 1.54624ms message: 'network-check-target-ip-10-0-139-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:16:21Z" - latency: 1.020463ms message: 'network-check-target-ip-10-0-139-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:15:21Z" - latency: 1.345485ms message: 'network-check-target-ip-10-0-139-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:14:21Z" - latency: 1.331592ms message: 'network-check-target-ip-10-0-139-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:13:21Z" - latency: 1.05621ms message: 'network-check-target-ip-10-0-139-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:12:21Z" - latency: 1.059733ms message: 'network-check-target-ip-10-0-139-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:11:21Z" - latency: 959.433µs message: 'network-check-target-ip-10-0-139-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:10:21Z" - latency: 942.368µs message: 'network-check-target-ip-10-0-139-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:09:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T20:50:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-214-to-network-check-target-ip-10-0-141-159 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-214.ec2.internal uid: 73fd6bd5-d3f0-4715-b3e3-f4b65256a672 resourceVersion: "46793" uid: 428ce40a-c530-4949-8702-b60780a93e3e spec: sourcePod: network-check-source-dbd9cf844-m7lkf targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-03T20:57:21Z" message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.024887ms message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:18:21Z" - latency: 2.244336ms message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:17:21Z" - latency: 2.367015ms message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:16:21Z" - latency: 2.37921ms message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:15:21Z" - latency: 2.245024ms message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:14:21Z" - latency: 2.120313ms message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:13:21Z" - latency: 2.201776ms message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:12:21Z" - latency: 2.127482ms message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:11:21Z" - latency: 2.187549ms message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:10:21Z" - latency: 2.394143ms message: 'network-check-target-ip-10-0-141-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:09:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T20:50:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-214-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-214.ec2.internal uid: 73fd6bd5-d3f0-4715-b3e3-f4b65256a672 resourceVersion: "48937" uid: 7691ba45-4b86-41a7-b022-0a37dd0276f7 spec: sourcePod: network-check-source-dbd9cf844-m7lkf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-03T20:56:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.184613ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:20:21Z" - latency: 1.741114ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T21:20:21Z" - latency: 897.469µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:19:21Z" - latency: 1.677066ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T21:19:21Z" - latency: 825.145µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:18:21Z" - latency: 2.008769ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T21:18:21Z" - latency: 931.502µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:17:21Z" - latency: 1.694207ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T21:17:21Z" - latency: 1.025713ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:16:21Z" - latency: 1.927331ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T21:16:21Z" kind: List metadata: resourceVersion: ""