apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:10:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-149-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-149.ec2.internal uid: cc7318df-58cf-44dd-8719-4266325818b2 resourceVersion: "45221" uid: 024128bb-7c92-4f15-a319-107d40826490 spec: sourcePod: network-check-source-dbd9cf844-q5djg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-08T12:17:32Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.203434ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:38:32Z" - latency: 1.592789ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:37:32Z" - latency: 1.178959ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:36:32Z" - latency: 1.258095ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:35:32Z" - latency: 808.123µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:34:32Z" - latency: 843.478µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:33:32Z" - latency: 1.359346ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:32:32Z" - latency: 1.066093ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:31:32Z" - latency: 1.12112ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:30:32Z" - latency: 821.25µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:29:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:10:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-149-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-149.ec2.internal uid: cc7318df-58cf-44dd-8719-4266325818b2 resourceVersion: "47258" uid: 71b8597d-2cfa-4a7e-a348-349fe7b55a75 spec: sourcePod: network-check-source-dbd9cf844-q5djg targetEndpoint: a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T12:16:32Z" message: 'load-balancer-api-external: tcp connection to a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.722899ms message: 'load-balancer-api-external: tcp connection to a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:40:32Z" - latency: 6.567325ms message: 'load-balancer-api-external: resolved host name a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:40:32Z" - latency: 5.621651ms message: 'load-balancer-api-external: tcp connection to a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:39:32Z" - latency: 6.99739ms message: 'load-balancer-api-external: resolved host name a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:39:32Z" - latency: 4.252916ms message: 'load-balancer-api-external: tcp connection to a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:38:32Z" - latency: 6.851306ms message: 'load-balancer-api-external: resolved host name a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:38:32Z" - latency: 5.582032ms message: 'load-balancer-api-external: tcp connection to a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:37:32Z" - latency: 7.326235ms message: 'load-balancer-api-external: resolved host name a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:37:32Z" - latency: 4.893402ms message: 'load-balancer-api-external: tcp connection to a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:36:32Z" - latency: 6.815059ms message: 'load-balancer-api-external: resolved host name a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:36:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:10:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-149-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-149.ec2.internal uid: cc7318df-58cf-44dd-8719-4266325818b2 resourceVersion: "47259" uid: a7c89597-e7f2-4fab-be8b-ce7b3d78e278 spec: sourcePod: network-check-source-dbd9cf844-q5djg targetEndpoint: a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T12:16:32Z" message: 'load-balancer-api-internal: tcp connection to a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.72727ms message: 'load-balancer-api-internal: tcp connection to a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:40:32Z" - latency: 6.632574ms message: 'load-balancer-api-internal: resolved host name a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:40:32Z" - latency: 5.552583ms message: 'load-balancer-api-internal: tcp connection to a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:39:32Z" - latency: 7.055082ms message: 'load-balancer-api-internal: resolved host name a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:39:32Z" - latency: 5.778751ms message: 'load-balancer-api-internal: tcp connection to a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:38:32Z" - latency: 6.926151ms message: 'load-balancer-api-internal: resolved host name a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:38:32Z" - latency: 4.621812ms message: 'load-balancer-api-internal: tcp connection to a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:37:32Z" - latency: 7.37611ms message: 'load-balancer-api-internal: resolved host name a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:37:32Z" - latency: 4.889239ms message: 'load-balancer-api-internal: tcp connection to a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:36:32Z" - latency: 6.922875ms message: 'load-balancer-api-internal: resolved host name a6a7e5254d4424937b9e288e87d37ac6-89247e07c30a2f56.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:36:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:10:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-149-to-network-check-target-ip-10-0-132-69 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-149.ec2.internal uid: cc7318df-58cf-44dd-8719-4266325818b2 resourceVersion: "45219" uid: 4602e979-7971-4491-9038-a5a7d7ee884c spec: sourcePod: network-check-source-dbd9cf844-q5djg targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-08T12:17:32Z" message: 'network-check-target-ip-10-0-132-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.918942ms message: 'network-check-target-ip-10-0-132-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:38:32Z" - latency: 2.129061ms message: 'network-check-target-ip-10-0-132-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:37:32Z" - latency: 1.86667ms message: 'network-check-target-ip-10-0-132-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:36:32Z" - latency: 2.206457ms message: 'network-check-target-ip-10-0-132-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:35:32Z" - latency: 2.210867ms message: 'network-check-target-ip-10-0-132-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:34:32Z" - latency: 1.743354ms message: 'network-check-target-ip-10-0-132-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:33:32Z" - latency: 2.201435ms message: 'network-check-target-ip-10-0-132-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:32:32Z" - latency: 1.961971ms message: 'network-check-target-ip-10-0-132-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:31:32Z" - latency: 1.901681ms message: 'network-check-target-ip-10-0-132-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:30:32Z" - latency: 1.596312ms message: 'network-check-target-ip-10-0-132-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:29:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:10:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-149-to-network-check-target-ip-10-0-133-35 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-149.ec2.internal uid: cc7318df-58cf-44dd-8719-4266325818b2 resourceVersion: "45220" uid: 1b928b01-05cc-4093-9953-812adb767989 spec: sourcePod: network-check-source-dbd9cf844-q5djg targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-08T12:17:32Z" message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.803522ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:38:32Z" - latency: 1.898941ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:37:32Z" - latency: 1.814292ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:36:32Z" - latency: 2.155746ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:35:32Z" - latency: 1.715157ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:34:32Z" - latency: 1.682147ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:33:32Z" - latency: 1.987126ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:32:32Z" - latency: 2.047664ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:31:32Z" - latency: 1.782591ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:30:32Z" - latency: 1.65327ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:29:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:10:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-149-to-network-check-target-ip-10-0-136-149 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-149.ec2.internal uid: cc7318df-58cf-44dd-8719-4266325818b2 resourceVersion: "45218" uid: c37f58e9-c9bf-4a0d-91e4-c41f02e9f2c1 spec: sourcePod: network-check-source-dbd9cf844-q5djg targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-08T12:17:32Z" message: 'network-check-target-ip-10-0-136-149: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.043897ms message: 'network-check-target-ip-10-0-136-149: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:38:32Z" - latency: 945.976µs message: 'network-check-target-ip-10-0-136-149: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:37:32Z" - latency: 904.496µs message: 'network-check-target-ip-10-0-136-149: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:36:32Z" - latency: 997.763µs message: 'network-check-target-ip-10-0-136-149: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:35:32Z" - latency: 961.575µs message: 'network-check-target-ip-10-0-136-149: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:34:32Z" - latency: 1.033628ms message: 'network-check-target-ip-10-0-136-149: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:33:32Z" - latency: 1.477746ms message: 'network-check-target-ip-10-0-136-149: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:32:32Z" - latency: 1.077691ms message: 'network-check-target-ip-10-0-136-149: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:31:32Z" - latency: 1.581711ms message: 'network-check-target-ip-10-0-136-149: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:30:32Z" - latency: 1.13582ms message: 'network-check-target-ip-10-0-136-149: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:29:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:10:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-149-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-149.ec2.internal uid: cc7318df-58cf-44dd-8719-4266325818b2 resourceVersion: "47257" uid: 98fd1ee3-5d01-4177-8956-f5ab2da6b886 spec: sourcePod: network-check-source-dbd9cf844-q5djg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-08T12:16:32Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.103591ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:40:32Z" - latency: 1.877386ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:40:32Z" - latency: 903.795µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:39:32Z" - latency: 1.975248ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:39:32Z" - latency: 838.244µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:38:32Z" - latency: 1.961651ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:38:32Z" - latency: 889.191µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:37:32Z" - latency: 1.903319ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:37:32Z" - latency: 1.026397ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:36:32Z" - latency: 2.023371ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:36:32Z" kind: List metadata: resourceVersion: ""