apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T15:38:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-154-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-154.ec2.internal uid: de3cd9d3-2fff-488e-b35f-eaa3b8632783 resourceVersion: "52924" uid: f64ec305-7b01-4ba9-99c2-1ba087a8441e spec: sourcePod: network-check-source-989f8b8dc-fkcxv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T15:45:07Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.028975ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:13:07Z" - latency: 1.160107ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:12:07Z" - latency: 1.197789ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:11:07Z" - latency: 1.581313ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:10:07Z" - latency: 901.938µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:09:07Z" - latency: 1.263102ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:08:07Z" - latency: 1.148651ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:07:07Z" - latency: 822.276µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:06:07Z" - latency: 1.234754ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:05:07Z" - latency: 806.505µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:04:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T15:38:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-154-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-154.ec2.internal uid: de3cd9d3-2fff-488e-b35f-eaa3b8632783 resourceVersion: "53824" uid: 0407a9c9-f141-41d1-a68f-6e5ed28cfb7d spec: sourcePod: network-check-source-989f8b8dc-fkcxv targetEndpoint: a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T15:44:07Z" message: 'load-balancer-api-external: tcp connection to a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.217819ms message: 'load-balancer-api-external: tcp connection to a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:14:07Z" - latency: 8.695199ms message: 'load-balancer-api-external: resolved host name a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T16:14:07Z" - latency: 4.412524ms message: 'load-balancer-api-external: tcp connection to a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:13:07Z" - latency: 9.4481ms message: 'load-balancer-api-external: resolved host name a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T16:13:07Z" - latency: 3.679359ms message: 'load-balancer-api-external: tcp connection to a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:12:07Z" - latency: 8.469022ms message: 'load-balancer-api-external: resolved host name a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T16:12:07Z" - latency: 10.903357ms message: 'load-balancer-api-external: tcp connection to a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:11:07Z" - latency: 11.37416ms message: 'load-balancer-api-external: resolved host name a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T16:11:07Z" - latency: 6.055707ms message: 'load-balancer-api-external: tcp connection to a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:10:07Z" - latency: 8.269654ms message: 'load-balancer-api-external: resolved host name a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T16:10:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T15:38:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-154-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-154.ec2.internal uid: de3cd9d3-2fff-488e-b35f-eaa3b8632783 resourceVersion: "53823" uid: 3f0c79c9-06b6-4741-bace-8994a4122af1 spec: sourcePod: network-check-source-989f8b8dc-fkcxv targetEndpoint: a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T15:44:07Z" message: 'load-balancer-api-internal: tcp connection to a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.14086ms message: 'load-balancer-api-internal: tcp connection to a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:14:07Z" - latency: 8.634315ms message: 'load-balancer-api-internal: resolved host name a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T16:14:07Z" - latency: 3.502412ms message: 'load-balancer-api-internal: tcp connection to a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:13:07Z" - latency: 9.399415ms message: 'load-balancer-api-internal: resolved host name a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T16:13:07Z" - latency: 3.667256ms message: 'load-balancer-api-internal: tcp connection to a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:12:07Z" - latency: 8.413248ms message: 'load-balancer-api-internal: resolved host name a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T16:12:07Z" - latency: 4.866846ms message: 'load-balancer-api-internal: tcp connection to a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:11:07Z" - latency: 11.460806ms message: 'load-balancer-api-internal: resolved host name a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T16:11:07Z" - latency: 6.065497ms message: 'load-balancer-api-internal: tcp connection to a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:10:07Z" - latency: 8.209756ms message: 'load-balancer-api-internal: resolved host name a3ad7522434b7441681386e136174463-75e9bd35375321b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T16:10:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T15:38:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-154-to-network-check-target-ip-10-0-129-154 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-154.ec2.internal uid: de3cd9d3-2fff-488e-b35f-eaa3b8632783 resourceVersion: "52922" uid: c3c680ce-a6a7-4f74-815f-1750e7f3fc6b spec: sourcePod: network-check-source-989f8b8dc-fkcxv targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T15:45:07Z" message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 974.901µs message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:13:07Z" - latency: 1.421208ms message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:12:07Z" - latency: 920.316µs message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:11:07Z" - latency: 1.485201ms message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:10:07Z" - latency: 844.839µs message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:09:07Z" - latency: 1.512094ms message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:08:07Z" - latency: 1.035773ms message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:07:07Z" - latency: 874.422µs message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:06:07Z" - latency: 1.134096ms message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:05:07Z" - latency: 1.268906ms message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:04:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T15:38:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-154-to-network-check-target-ip-10-0-131-241 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-154.ec2.internal uid: de3cd9d3-2fff-488e-b35f-eaa3b8632783 resourceVersion: "52921" uid: c756d8ba-3029-4180-a631-e889959a028c spec: sourcePod: network-check-source-989f8b8dc-fkcxv targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T15:45:07Z" message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.199602ms message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:13:07Z" - latency: 2.640454ms message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:12:07Z" - latency: 2.671689ms message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:11:07Z" - latency: 2.312159ms message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:10:07Z" - latency: 2.104554ms message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:09:07Z" - latency: 2.178021ms message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:08:07Z" - latency: 2.243992ms message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:07:07Z" - latency: 2.453786ms message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:06:07Z" - latency: 1.739476ms message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:05:07Z" - latency: 2.121746ms message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:04:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T15:38:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-154-to-network-check-target-ip-10-0-138-21 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-154.ec2.internal uid: de3cd9d3-2fff-488e-b35f-eaa3b8632783 resourceVersion: "52923" uid: 504fc367-e0e9-41fe-94b8-1a4064fd5d1b spec: sourcePod: network-check-source-989f8b8dc-fkcxv targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T15:45:07Z" message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.131887ms message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:13:07Z" - latency: 2.34859ms message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:12:07Z" - latency: 2.542453ms message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:11:07Z" - latency: 2.816511ms message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:10:07Z" - latency: 2.385639ms message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:09:07Z" - latency: 2.388296ms message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:08:07Z" - latency: 2.350152ms message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:07:07Z" - latency: 2.407809ms message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:06:07Z" - latency: 2.249745ms message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:05:07Z" - latency: 2.739441ms message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:04:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T15:38:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-154-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-154.ec2.internal uid: de3cd9d3-2fff-488e-b35f-eaa3b8632783 resourceVersion: "53822" uid: 3e7bff6e-16af-4b28-bacd-d1beb7942bb8 spec: sourcePod: network-check-source-989f8b8dc-fkcxv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T15:44:07Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 763.6µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:14:07Z" - latency: 1.75487ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T16:14:07Z" - latency: 1.04446ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:13:07Z" - latency: 2.14796ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T16:13:07Z" - latency: 1.217028ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:12:07Z" - latency: 1.735163ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T16:12:07Z" - latency: 904.995µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:11:07Z" - latency: 1.70767ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T16:11:07Z" - latency: 1.13522ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T16:10:07Z" - latency: 2.074288ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T16:10:07Z" kind: List metadata: resourceVersion: ""