apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T17:47:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-90-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-90.ec2.internal uid: c06272a2-59da-4ddd-9dcb-8c6d0813761e resourceVersion: "43322" uid: fdd5e331-a6a6-46fb-9e27-6239299458be spec: sourcePod: network-check-source-7f44b6dd87-hswjp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-27T17:54:52Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 988.163µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:15:52Z" - latency: 803.795µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:14:52Z" - latency: 677.562µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:13:52Z" - latency: 731.567µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:12:52Z" - latency: 1.0175ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:11:52Z" - latency: 888.105µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:10:52Z" - latency: 997.486µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:09:52Z" - latency: 693.313µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:08:52Z" - latency: 1.341653ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:07:52Z" - latency: 796.733µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:06:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T17:47:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-90-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-90.ec2.internal uid: c06272a2-59da-4ddd-9dcb-8c6d0813761e resourceVersion: "45913" uid: 280bf495-08f9-490b-8e34-fe355fc6b71b spec: sourcePod: network-check-source-7f44b6dd87-hswjp targetEndpoint: ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-27T17:53:52Z" message: 'load-balancer-api-external: tcp connection to ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.609679ms message: 'load-balancer-api-external: tcp connection to ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:17:52Z" - latency: 7.506402ms message: 'load-balancer-api-external: resolved host name ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T18:17:52Z" - latency: 4.243693ms message: 'load-balancer-api-external: tcp connection to ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:16:52Z" - latency: 7.897122ms message: 'load-balancer-api-external: resolved host name ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T18:16:52Z" - latency: 3.751076ms message: 'load-balancer-api-external: tcp connection to ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:15:52Z" - latency: 8.078506ms message: 'load-balancer-api-external: resolved host name ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T18:15:52Z" - latency: 5.608008ms message: 'load-balancer-api-external: tcp connection to ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:14:52Z" - latency: 7.781328ms message: 'load-balancer-api-external: resolved host name ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T18:14:52Z" - latency: 5.870614ms message: 'load-balancer-api-external: tcp connection to ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:13:52Z" - latency: 7.362644ms message: 'load-balancer-api-external: resolved host name ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T18:13:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T17:47:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-90-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-90.ec2.internal uid: c06272a2-59da-4ddd-9dcb-8c6d0813761e resourceVersion: "45912" uid: d70b9ac3-8ed0-4ce7-ae40-4f826745ab00 spec: sourcePod: network-check-source-7f44b6dd87-hswjp targetEndpoint: ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-27T17:53:52Z" message: 'load-balancer-api-internal: tcp connection to ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.581759ms message: 'load-balancer-api-internal: tcp connection to ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:17:52Z" - latency: 7.419302ms message: 'load-balancer-api-internal: resolved host name ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T18:17:52Z" - latency: 4.964866ms message: 'load-balancer-api-internal: tcp connection to ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:16:52Z" - latency: 8.014301ms message: 'load-balancer-api-internal: resolved host name ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T18:16:52Z" - latency: 3.807274ms message: 'load-balancer-api-internal: tcp connection to ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:15:52Z" - latency: 8.043093ms message: 'load-balancer-api-internal: resolved host name ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T18:15:52Z" - latency: 5.75293ms message: 'load-balancer-api-internal: tcp connection to ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:14:52Z" - latency: 7.885514ms message: 'load-balancer-api-internal: resolved host name ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T18:14:52Z" - latency: 4.334481ms message: 'load-balancer-api-internal: tcp connection to ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:13:52Z" - latency: 7.312198ms message: 'load-balancer-api-internal: resolved host name ae2e12fc9bace46a1bdf224476461dcd-f1a1838babbe506b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T18:13:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T17:47:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-90-to-network-check-target-ip-10-0-129-78 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-90.ec2.internal uid: c06272a2-59da-4ddd-9dcb-8c6d0813761e resourceVersion: "43321" uid: 9087c66a-b4ce-499d-af63-3352ac9070ac spec: sourcePod: network-check-source-7f44b6dd87-hswjp targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-27T17:54:52Z" message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.906332ms message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:15:52Z" - latency: 2.129619ms message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:14:52Z" - latency: 1.852751ms message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:13:52Z" - latency: 1.930006ms message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:12:52Z" - latency: 2.289152ms message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:11:52Z" - latency: 1.833937ms message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:10:52Z" - latency: 1.736945ms message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:09:52Z" - latency: 2.032006ms message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:08:52Z" - latency: 1.933742ms message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:07:52Z" - latency: 1.771605ms message: 'network-check-target-ip-10-0-129-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:06:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T17:47:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-90-to-network-check-target-ip-10-0-135-90 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-90.ec2.internal uid: c06272a2-59da-4ddd-9dcb-8c6d0813761e resourceVersion: "43320" uid: 0ac6182a-4201-403d-ba41-0d56f4e7bc6a spec: sourcePod: network-check-source-7f44b6dd87-hswjp targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-27T17:54:52Z" message: 'network-check-target-ip-10-0-135-90: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.303634ms message: 'network-check-target-ip-10-0-135-90: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:15:52Z" - latency: 1.228194ms message: 'network-check-target-ip-10-0-135-90: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:14:52Z" - latency: 624.149µs message: 'network-check-target-ip-10-0-135-90: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:13:52Z" - latency: 728.54µs message: 'network-check-target-ip-10-0-135-90: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:12:52Z" - latency: 743.602µs message: 'network-check-target-ip-10-0-135-90: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:11:52Z" - latency: 818.516µs message: 'network-check-target-ip-10-0-135-90: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:10:52Z" - latency: 964.263µs message: 'network-check-target-ip-10-0-135-90: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:09:52Z" - latency: 847.645µs message: 'network-check-target-ip-10-0-135-90: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:08:52Z" - latency: 791.583µs message: 'network-check-target-ip-10-0-135-90: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:07:52Z" - latency: 734.746µs message: 'network-check-target-ip-10-0-135-90: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:06:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T17:47:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-90-to-network-check-target-ip-10-0-141-245 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-90.ec2.internal uid: c06272a2-59da-4ddd-9dcb-8c6d0813761e resourceVersion: "43319" uid: f4e9797a-6c9e-4255-bccd-c0cbe9e05e31 spec: sourcePod: network-check-source-7f44b6dd87-hswjp targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-27T17:54:52Z" message: 'network-check-target-ip-10-0-141-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.623655ms message: 'network-check-target-ip-10-0-141-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:15:52Z" - latency: 1.64671ms message: 'network-check-target-ip-10-0-141-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:14:52Z" - latency: 1.430881ms message: 'network-check-target-ip-10-0-141-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:13:52Z" - latency: 1.637486ms message: 'network-check-target-ip-10-0-141-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:12:52Z" - latency: 1.745184ms message: 'network-check-target-ip-10-0-141-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:11:52Z" - latency: 1.770399ms message: 'network-check-target-ip-10-0-141-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:10:52Z" - latency: 1.929608ms message: 'network-check-target-ip-10-0-141-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:09:52Z" - latency: 1.697728ms message: 'network-check-target-ip-10-0-141-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:08:52Z" - latency: 1.848891ms message: 'network-check-target-ip-10-0-141-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:07:52Z" - latency: 1.64157ms message: 'network-check-target-ip-10-0-141-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:06:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T17:47:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-90-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-90.ec2.internal uid: c06272a2-59da-4ddd-9dcb-8c6d0813761e resourceVersion: "45911" uid: 26167265-82e7-400e-aac8-2daadd7bf87d spec: sourcePod: network-check-source-7f44b6dd87-hswjp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-27T17:53:52Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.125405ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:17:52Z" - latency: 1.62758ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T18:17:52Z" - latency: 781.369µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:16:52Z" - latency: 1.730475ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T18:16:52Z" - latency: 821.904µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:15:52Z" - latency: 1.575938ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T18:15:52Z" - latency: 680.906µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:14:52Z" - latency: 1.681242ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T18:14:52Z" - latency: 722.572µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T18:13:52Z" - latency: 1.639558ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T18:13:52Z" kind: List metadata: resourceVersion: ""