apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T12:25:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-136-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-136.ec2.internal uid: 913cfbe0-5473-4518-aa5c-daeef8b3c890 resourceVersion: "14982" uid: e63d2858-10b5-4f00-afa5-c5ba7b458643 spec: sourcePod: network-check-source-685456655f-84vwp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-10T12:32:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.893609ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:32:51Z" - latency: 1.272762ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:31:51Z" - latency: 1.359517ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:30:51Z" - latency: 1.174257ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:29:51Z" - latency: 983.073µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:28:51Z" - latency: 840.992µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:27:51Z" - latency: 1.279017ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:26:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T12:25:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-136-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-136.ec2.internal uid: 913cfbe0-5473-4518-aa5c-daeef8b3c890 resourceVersion: "17128" uid: f794ba6c-9164-457a-8ce5-ad9714eea384 spec: sourcePod: network-check-source-685456655f-84vwp targetEndpoint: a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T12:31:51Z" message: 'load-balancer-api-external: tcp connection to a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.134735ms message: 'load-balancer-api-external: tcp connection to a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:37:51Z" - latency: 6.981051ms message: 'load-balancer-api-external: resolved host name a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:37:51Z" - latency: 4.263755ms message: 'load-balancer-api-external: tcp connection to a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:36:51Z" - latency: 7.213138ms message: 'load-balancer-api-external: resolved host name a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:36:51Z" - latency: 4.931985ms message: 'load-balancer-api-external: tcp connection to a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:35:51Z" - latency: 9.172276ms message: 'load-balancer-api-external: resolved host name a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:35:51Z" - latency: 5.440079ms message: 'load-balancer-api-external: tcp connection to a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:34:51Z" - latency: 6.810489ms message: 'load-balancer-api-external: resolved host name a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:34:51Z" - latency: 4.182663ms message: 'load-balancer-api-external: tcp connection to a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:33:51Z" - latency: 7.15579ms message: 'load-balancer-api-external: resolved host name a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:33:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T12:25:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-136-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-136.ec2.internal uid: 913cfbe0-5473-4518-aa5c-daeef8b3c890 resourceVersion: "17127" uid: b9918979-6817-41a0-a46a-60152d2c87ae spec: sourcePod: network-check-source-685456655f-84vwp targetEndpoint: a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T12:31:51Z" message: 'load-balancer-api-internal: tcp connection to a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.098595ms message: 'load-balancer-api-internal: tcp connection to a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:37:51Z" - latency: 7.05673ms message: 'load-balancer-api-internal: resolved host name a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:37:51Z" - latency: 4.207172ms message: 'load-balancer-api-internal: tcp connection to a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:36:51Z" - latency: 7.46729ms message: 'load-balancer-api-internal: resolved host name a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:36:51Z" - latency: 4.883433ms message: 'load-balancer-api-internal: tcp connection to a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:35:51Z" - latency: 9.483866ms message: 'load-balancer-api-internal: resolved host name a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:35:51Z" - latency: 4.842286ms message: 'load-balancer-api-internal: tcp connection to a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:34:51Z" - latency: 6.858189ms message: 'load-balancer-api-internal: resolved host name a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:34:51Z" - latency: 4.178583ms message: 'load-balancer-api-internal: tcp connection to a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:33:51Z" - latency: 7.230999ms message: 'load-balancer-api-internal: resolved host name a59203f0ed6b84cb7a5eaa80709ae3fc-6a018bdd6920fa59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T12:33:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T12:25:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-136-to-network-check-target-ip-10-0-128-201 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-136.ec2.internal uid: 913cfbe0-5473-4518-aa5c-daeef8b3c890 resourceVersion: "14981" uid: 531d0f46-9860-440e-8494-c62262bb5d65 spec: sourcePod: network-check-source-685456655f-84vwp targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-10T12:32:51Z" message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.005072ms message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:32:51Z" - latency: 2.076647ms message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:31:51Z" - latency: 2.139193ms message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:30:51Z" - latency: 2.34893ms message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:29:51Z" - latency: 2.443612ms message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:28:51Z" - latency: 2.221346ms message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:27:51Z" - latency: 1.865774ms message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:26:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T12:25:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-136-to-network-check-target-ip-10-0-130-132 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-136.ec2.internal uid: 913cfbe0-5473-4518-aa5c-daeef8b3c890 resourceVersion: "14980" uid: 4f7a2606-5cfa-4b93-b6d3-634f92271e15 spec: sourcePod: network-check-source-685456655f-84vwp targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-10T12:32:51Z" message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.39538ms message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:32:51Z" - latency: 1.829122ms message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:31:51Z" - latency: 1.94324ms message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:30:51Z" - latency: 1.822501ms message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:29:51Z" - latency: 1.894485ms message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:28:51Z" - latency: 1.981933ms message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:27:51Z" - latency: 1.932208ms message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:26:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T12:25:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-136-to-network-check-target-ip-10-0-130-136 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-136.ec2.internal uid: 913cfbe0-5473-4518-aa5c-daeef8b3c890 resourceVersion: "14979" uid: a74e9574-f380-4aa8-8647-628b57d860f6 spec: sourcePod: network-check-source-685456655f-84vwp targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-10T12:32:51Z" message: 'network-check-target-ip-10-0-130-136: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.006564ms message: 'network-check-target-ip-10-0-130-136: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:32:51Z" - latency: 927.159µs message: 'network-check-target-ip-10-0-130-136: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:31:51Z" - latency: 735.465µs message: 'network-check-target-ip-10-0-130-136: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:30:51Z" - latency: 1.119551ms message: 'network-check-target-ip-10-0-130-136: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:29:51Z" - latency: 1.167969ms message: 'network-check-target-ip-10-0-130-136: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:28:51Z" - latency: 893.283µs message: 'network-check-target-ip-10-0-130-136: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:27:51Z" - latency: 1.703023ms message: 'network-check-target-ip-10-0-130-136: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:26:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T12:25:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-136-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-136.ec2.internal uid: 913cfbe0-5473-4518-aa5c-daeef8b3c890 resourceVersion: "17126" uid: b940863a-ed47-41ec-ad9f-9289d1ed216d spec: sourcePod: network-check-source-685456655f-84vwp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-10T12:31:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 808.84µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:37:51Z" - latency: 1.750321ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T12:37:51Z" - latency: 985.733µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:36:51Z" - latency: 2.388617ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T12:36:51Z" - latency: 1.101914ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:35:51Z" - latency: 2.398851ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T12:35:51Z" - latency: 923.201µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:34:51Z" - latency: 2.045263ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T12:34:51Z" - latency: 1.202163ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T12:33:51Z" - latency: 1.76021ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T12:33:51Z" kind: List metadata: resourceVersion: ""