apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:31:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-249-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-249.ec2.internal uid: a211cec4-e037-43e4-bdc6-e2b98fda7898 resourceVersion: "62694" uid: 92362f1e-4228-4677-bbab-8cda73385e26 spec: sourcePod: network-check-source-7bc5b6bf85-4lxjv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-22T02:38:09Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 828.22µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:13:09Z" - latency: 869.138µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:12:09Z" - latency: 1.303178ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:11:09Z" - latency: 1.004451ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:10:09Z" - latency: 984.492µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:09:09Z" - latency: 1.65895ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:08:09Z" - latency: 1.002513ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:07:09Z" - latency: 1.040155ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:06:09Z" - latency: 1.181206ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:05:09Z" - latency: 1.114369ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:04:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:31:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-249-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-249.ec2.internal uid: a211cec4-e037-43e4-bdc6-e2b98fda7898 resourceVersion: "62696" uid: b2c2b3e7-ae77-4593-99e8-22b4bb975e1a spec: sourcePod: network-check-source-7bc5b6bf85-4lxjv targetEndpoint: a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T02:37:09Z" message: 'load-balancer-api-external: tcp connection to a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.808061ms message: 'load-balancer-api-external: tcp connection to a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:13:09Z" - latency: 6.8969ms message: 'load-balancer-api-external: resolved host name a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:13:09Z" - latency: 5.1426ms message: 'load-balancer-api-external: tcp connection to a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:12:09Z" - latency: 7.51558ms message: 'load-balancer-api-external: resolved host name a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:12:09Z" - latency: 4.569001ms message: 'load-balancer-api-external: tcp connection to a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:11:09Z" - latency: 6.538665ms message: 'load-balancer-api-external: resolved host name a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:11:09Z" - latency: 4.838161ms message: 'load-balancer-api-external: tcp connection to a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:10:09Z" - latency: 7.737066ms message: 'load-balancer-api-external: resolved host name a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:10:09Z" - latency: 5.323971ms message: 'load-balancer-api-external: tcp connection to a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:09:09Z" - latency: 7.425776ms message: 'load-balancer-api-external: resolved host name a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:09:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:31:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-249-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-249.ec2.internal uid: a211cec4-e037-43e4-bdc6-e2b98fda7898 resourceVersion: "62695" uid: 35d7cd7b-dbbf-427e-9c6a-aa1c0bc16d5a spec: sourcePod: network-check-source-7bc5b6bf85-4lxjv targetEndpoint: a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T02:37:09Z" message: 'load-balancer-api-internal: tcp connection to a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.172882ms message: 'load-balancer-api-internal: tcp connection to a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:13:09Z" - latency: 6.913347ms message: 'load-balancer-api-internal: resolved host name a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:13:09Z" - latency: 5.352068ms message: 'load-balancer-api-internal: tcp connection to a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:12:09Z" - latency: 7.414719ms message: 'load-balancer-api-internal: resolved host name a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:12:09Z" - latency: 4.904217ms message: 'load-balancer-api-internal: tcp connection to a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:11:09Z" - latency: 6.622092ms message: 'load-balancer-api-internal: resolved host name a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:11:09Z" - latency: 4.87025ms message: 'load-balancer-api-internal: tcp connection to a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:10:09Z" - latency: 7.772195ms message: 'load-balancer-api-internal: resolved host name a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:10:09Z" - latency: 5.324113ms message: 'load-balancer-api-internal: tcp connection to a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:09:09Z" - latency: 7.507212ms message: 'load-balancer-api-internal: resolved host name a37d9ce3dc19d4ccc85afb627a5fa0e4-e4c64130344678fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T03:09:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:31:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-249-to-network-check-target-ip-10-0-130-249 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-249.ec2.internal uid: a211cec4-e037-43e4-bdc6-e2b98fda7898 resourceVersion: "62690" uid: 382574b6-dd02-4b1c-8aca-f746bfa7c594 spec: sourcePod: network-check-source-7bc5b6bf85-4lxjv targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T02:38:09Z" message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.024188ms message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:13:09Z" - latency: 1.336177ms message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:12:09Z" - latency: 1.019947ms message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:11:09Z" - latency: 896.151µs message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:10:09Z" - latency: 1.671631ms message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:09:09Z" - latency: 869.007µs message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:08:09Z" - latency: 1.002257ms message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:07:09Z" - latency: 878.394µs message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:06:09Z" - latency: 1.027828ms message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:05:09Z" - latency: 1.176746ms message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:04:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:31:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-249-to-network-check-target-ip-10-0-133-125 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-249.ec2.internal uid: a211cec4-e037-43e4-bdc6-e2b98fda7898 resourceVersion: "62692" uid: a8d0403e-f329-4177-b528-55f257d2c408 spec: sourcePod: network-check-source-7bc5b6bf85-4lxjv targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T02:38:09Z" message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.44409ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:13:09Z" - latency: 2.441442ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:12:09Z" - latency: 2.375273ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:11:09Z" - latency: 2.294782ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:10:09Z" - latency: 2.621916ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:09:09Z" - latency: 2.310555ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:08:09Z" - latency: 2.303043ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:07:09Z" - latency: 2.789113ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:06:09Z" - latency: 2.47157ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:05:09Z" - latency: 2.572834ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:04:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:31:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-249-to-network-check-target-ip-10-0-133-30 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-249.ec2.internal uid: a211cec4-e037-43e4-bdc6-e2b98fda7898 resourceVersion: "62691" uid: cbfb7316-ad33-48e1-8d73-23034bbdd2d2 spec: sourcePod: network-check-source-7bc5b6bf85-4lxjv targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T02:38:09Z" message: 'network-check-target-ip-10-0-133-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.446197ms message: 'network-check-target-ip-10-0-133-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:13:09Z" - latency: 2.036695ms message: 'network-check-target-ip-10-0-133-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:12:09Z" - latency: 2.480325ms message: 'network-check-target-ip-10-0-133-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:11:09Z" - latency: 2.193739ms message: 'network-check-target-ip-10-0-133-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:10:09Z" - latency: 2.674404ms message: 'network-check-target-ip-10-0-133-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:09:09Z" - latency: 2.124848ms message: 'network-check-target-ip-10-0-133-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:08:09Z" - latency: 2.107869ms message: 'network-check-target-ip-10-0-133-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:07:09Z" - latency: 2.406572ms message: 'network-check-target-ip-10-0-133-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:06:09Z" - latency: 2.453281ms message: 'network-check-target-ip-10-0-133-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:05:09Z" - latency: 2.841076ms message: 'network-check-target-ip-10-0-133-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:04:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T02:31:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-249-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-249.ec2.internal uid: a211cec4-e037-43e4-bdc6-e2b98fda7898 resourceVersion: "62693" uid: 08411beb-36cb-4891-8564-0bad4dc81f39 spec: sourcePod: network-check-source-7bc5b6bf85-4lxjv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-22T02:37:09Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.030169ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:13:09Z" - latency: 1.976455ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T03:13:09Z" - latency: 952.11µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:12:09Z" - latency: 1.70423ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T03:12:09Z" - latency: 931.202µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:11:09Z" - latency: 1.697818ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T03:11:09Z" - latency: 1.09788ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:10:09Z" - latency: 1.783337ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T03:10:09Z" - latency: 1.289638ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T03:09:09Z" - latency: 2.176566ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T03:09:09Z" kind: List metadata: resourceVersion: ""