apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T23:49:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-145-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-145.ec2.internal uid: efffd2bd-4344-466f-8fa6-61da64d0d644 resourceVersion: "19881" uid: 52cbecc7-6098-4b99-bffd-3c569c3904db spec: sourcePod: network-check-source-7f44b6dd87-jqvtb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-26T23:56:42Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.021544ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:10:42Z" - latency: 904.353µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:09:42Z" - latency: 880.037µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:08:42Z" - latency: 1.185964ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:07:42Z" - latency: 912.115µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:06:42Z" - latency: 1.080822ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:05:42Z" - latency: 821.58µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:04:42Z" - latency: 1.080171ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:03:42Z" - latency: 1.004476ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:02:42Z" - latency: 907.069µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:01:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T23:49:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-145-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-145.ec2.internal uid: efffd2bd-4344-466f-8fa6-61da64d0d644 resourceVersion: "21114" uid: c2a1a461-f103-42f5-bbd4-c2c1e83ace35 spec: sourcePod: network-check-source-7f44b6dd87-jqvtb targetEndpoint: a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T23:55:42Z" message: 'load-balancer-api-external: tcp connection to a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.25086ms message: 'load-balancer-api-external: tcp connection to a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:13:42Z" - latency: 6.547512ms message: 'load-balancer-api-external: resolved host name a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T00:13:42Z" - latency: 6.004533ms message: 'load-balancer-api-external: tcp connection to a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:12:42Z" - latency: 7.550883ms message: 'load-balancer-api-external: resolved host name a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T00:12:42Z" - latency: 5.430473ms message: 'load-balancer-api-external: tcp connection to a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:11:42Z" - latency: 8.047809ms message: 'load-balancer-api-external: resolved host name a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T00:11:42Z" - latency: 5.436983ms message: 'load-balancer-api-external: tcp connection to a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:10:42Z" - latency: 7.766192ms message: 'load-balancer-api-external: resolved host name a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T00:10:42Z" - latency: 4.391921ms message: 'load-balancer-api-external: tcp connection to a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:09:42Z" - latency: 8.802464ms message: 'load-balancer-api-external: resolved host name a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T00:09:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T23:49:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-145-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-145.ec2.internal uid: efffd2bd-4344-466f-8fa6-61da64d0d644 resourceVersion: "21115" uid: 84a251f1-d5b3-45d9-a6bc-a8955a288e05 spec: sourcePod: network-check-source-7f44b6dd87-jqvtb targetEndpoint: a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T23:55:42Z" message: 'load-balancer-api-internal: tcp connection to a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.120022ms message: 'load-balancer-api-internal: tcp connection to a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:13:42Z" - latency: 6.434942ms message: 'load-balancer-api-internal: resolved host name a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T00:13:42Z" - latency: 5.968646ms message: 'load-balancer-api-internal: tcp connection to a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:12:42Z" - latency: 7.59893ms message: 'load-balancer-api-internal: resolved host name a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T00:12:42Z" - latency: 6.537392ms message: 'load-balancer-api-internal: tcp connection to a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:11:42Z" - latency: 7.970962ms message: 'load-balancer-api-internal: resolved host name a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T00:11:42Z" - latency: 5.446879ms message: 'load-balancer-api-internal: tcp connection to a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:10:42Z" - latency: 7.673395ms message: 'load-balancer-api-internal: resolved host name a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T00:10:42Z" - latency: 5.028314ms message: 'load-balancer-api-internal: tcp connection to a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:09:42Z" - latency: 8.732744ms message: 'load-balancer-api-internal: resolved host name a392b1d7a02474cfcb02e92e99f33f04-a5cfa0631d229be2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T00:09:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T23:49:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-145-to-network-check-target-ip-10-0-128-145 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-145.ec2.internal uid: efffd2bd-4344-466f-8fa6-61da64d0d644 resourceVersion: "19878" uid: de81c881-9e95-4299-ba2f-bdc647c9b3aa spec: sourcePod: network-check-source-7f44b6dd87-jqvtb targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-26T23:56:42Z" message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 955.046µs message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:10:42Z" - latency: 824.811µs message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:09:42Z" - latency: 1.799835ms message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:08:42Z" - latency: 916.687µs message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:07:42Z" - latency: 854.709µs message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:06:42Z" - latency: 855.99µs message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:05:42Z" - latency: 1.003695ms message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:04:42Z" - latency: 956.178µs message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:03:42Z" - latency: 797.127µs message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:02:42Z" - latency: 1.301001ms message: 'network-check-target-ip-10-0-128-145: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:01:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T23:49:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-145-to-network-check-target-ip-10-0-136-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-145.ec2.internal uid: efffd2bd-4344-466f-8fa6-61da64d0d644 resourceVersion: "19880" uid: 153d9d68-6fa3-4424-ba62-d47f9b9a6c28 spec: sourcePod: network-check-source-7f44b6dd87-jqvtb targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-26T23:56:42Z" message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.164959ms message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:10:42Z" - latency: 2.143438ms message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:09:42Z" - latency: 1.776297ms message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:08:42Z" - latency: 2.518819ms message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:07:42Z" - latency: 2.205397ms message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:06:42Z" - latency: 2.527267ms message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:05:42Z" - latency: 1.808674ms message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:04:42Z" - latency: 2.177604ms message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:03:42Z" - latency: 2.346234ms message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:02:42Z" - latency: 2.390354ms message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:01:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T23:49:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-145-to-network-check-target-ip-10-0-136-129 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-145.ec2.internal uid: efffd2bd-4344-466f-8fa6-61da64d0d644 resourceVersion: "19879" uid: dff10df8-574f-4ade-8866-7727180a1e5c spec: sourcePod: network-check-source-7f44b6dd87-jqvtb targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-26T23:56:42Z" message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.552786ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:10:42Z" - latency: 2.06868ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:09:42Z" - latency: 2.023566ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:08:42Z" - latency: 2.418677ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:07:42Z" - latency: 2.273121ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:06:42Z" - latency: 2.157574ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:05:42Z" - latency: 2.140643ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:04:42Z" - latency: 2.290728ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:03:42Z" - latency: 2.64952ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:02:42Z" - latency: 2.390256ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:01:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T23:49:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-145-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-145.ec2.internal uid: efffd2bd-4344-466f-8fa6-61da64d0d644 resourceVersion: "21113" uid: 0ef46156-5227-4129-a138-a2c80b7b1d32 spec: sourcePod: network-check-source-7f44b6dd87-jqvtb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-26T23:55:42Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.055613ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:13:42Z" - latency: 1.595274ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T00:13:42Z" - latency: 871.566µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:12:42Z" - latency: 1.743944ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T00:12:42Z" - latency: 781.363µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:11:42Z" - latency: 1.607455ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T00:11:42Z" - latency: 1.366176ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:10:42Z" - latency: 1.562763ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T00:10:42Z" - latency: 875.434µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T00:09:42Z" - latency: 2.513578ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T00:09:42Z" kind: List metadata: resourceVersion: ""