apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T17:42:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-211-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-211.ec2.internal
      uid: fbf5ff39-d42e-42b4-ab17-694030cdf7e2
    resourceVersion: "22531"
    uid: 1a4fb48c-a9c3-47e0-8d65-80c4c6664be7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kthcm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T17:49:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.183937ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:49:37Z"
    - latency: 981.051µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:48:37Z"
    - latency: 1.175575ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:47:37Z"
    - latency: 1.196332ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:46:37Z"
    - latency: 923.245µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:45:37Z"
    - latency: 1.064964ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:44:37Z"
    - latency: 1.074429ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:43:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T17:42:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-211-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-211.ec2.internal
      uid: fbf5ff39-d42e-42b4-ab17-694030cdf7e2
    resourceVersion: "21312"
    uid: e301e979-b1cc-423e-bc73-7aef6caf72c0
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kthcm
    targetEndpoint: adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T17:48:37Z"
      message: 'load-balancer-api-external: tcp connection to adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.242786ms
      message: 'load-balancer-api-external: tcp connection to adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:48:37Z"
    - latency: 8.55702ms
      message: 'load-balancer-api-external: resolved host name adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:48:37Z"
    - latency: 3.293257ms
      message: 'load-balancer-api-external: tcp connection to adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:47:37Z"
    - latency: 9.646226ms
      message: 'load-balancer-api-external: resolved host name adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:47:37Z"
    - latency: 3.611513ms
      message: 'load-balancer-api-external: tcp connection to adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:46:37Z"
    - latency: 10.612247ms
      message: 'load-balancer-api-external: resolved host name adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:46:37Z"
    - latency: 4.415889ms
      message: 'load-balancer-api-external: tcp connection to adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:45:37Z"
    - latency: 9.204441ms
      message: 'load-balancer-api-external: resolved host name adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:45:37Z"
    - latency: 5.260897ms
      message: 'load-balancer-api-external: tcp connection to adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:44:37Z"
    - latency: 13.897685ms
      message: 'load-balancer-api-external: resolved host name adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:44:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T17:42:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-211-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-211.ec2.internal
      uid: fbf5ff39-d42e-42b4-ab17-694030cdf7e2
    resourceVersion: "21313"
    uid: 754f2e95-aba3-4499-bf08-0abcd316f456
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kthcm
    targetEndpoint: adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T17:48:37Z"
      message: 'load-balancer-api-internal: tcp connection to adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.393475ms
      message: 'load-balancer-api-internal: tcp connection to adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:48:37Z"
    - latency: 8.518131ms
      message: 'load-balancer-api-internal: resolved host name adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:48:37Z"
    - latency: 3.301508ms
      message: 'load-balancer-api-internal: tcp connection to adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:47:37Z"
    - latency: 9.668799ms
      message: 'load-balancer-api-internal: resolved host name adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:47:37Z"
    - latency: 3.820538ms
      message: 'load-balancer-api-internal: tcp connection to adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:46:37Z"
    - latency: 10.649916ms
      message: 'load-balancer-api-internal: resolved host name adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:46:37Z"
    - latency: 5.031359ms
      message: 'load-balancer-api-internal: tcp connection to adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:45:37Z"
    - latency: 9.29615ms
      message: 'load-balancer-api-internal: resolved host name adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:45:37Z"
    - latency: 3.982678ms
      message: 'load-balancer-api-internal: tcp connection to adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:44:37Z"
    - latency: 13.924953ms
      message: 'load-balancer-api-internal: resolved host name adbc203b34fd44aaebb3877f7bf57439-91da2c14beac8db5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:44:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T17:42:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-211-to-network-check-target-ip-10-0-133-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-211.ec2.internal
      uid: fbf5ff39-d42e-42b4-ab17-694030cdf7e2
    resourceVersion: "22528"
    uid: bfcf9ca1-1e9d-451b-b2db-aabf8b1c5df5
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kthcm
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T17:49:37Z"
      message: 'network-check-target-ip-10-0-133-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.137971ms
      message: 'network-check-target-ip-10-0-133-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:49:37Z"
    - latency: 2.31668ms
      message: 'network-check-target-ip-10-0-133-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:48:37Z"
    - latency: 1.979957ms
      message: 'network-check-target-ip-10-0-133-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:47:37Z"
    - latency: 2.588969ms
      message: 'network-check-target-ip-10-0-133-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:46:37Z"
    - latency: 2.307872ms
      message: 'network-check-target-ip-10-0-133-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:45:37Z"
    - latency: 2.293466ms
      message: 'network-check-target-ip-10-0-133-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:44:37Z"
    - latency: 2.471279ms
      message: 'network-check-target-ip-10-0-133-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:43:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T17:42:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-211-to-network-check-target-ip-10-0-135-211
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-211.ec2.internal
      uid: fbf5ff39-d42e-42b4-ab17-694030cdf7e2
    resourceVersion: "22527"
    uid: 365a8f1a-d92d-4c65-a8b8-fe7064dc9a86
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kthcm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T17:49:37Z"
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 950.134µs
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:49:37Z"
    - latency: 946.144µs
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:48:37Z"
    - latency: 869.321µs
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:47:37Z"
    - latency: 977.101µs
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:46:37Z"
    - latency: 1.069546ms
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:45:37Z"
    - latency: 1.695334ms
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:44:37Z"
    - latency: 1.762101ms
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:43:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T17:42:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-211-to-network-check-target-ip-10-0-143-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-211.ec2.internal
      uid: fbf5ff39-d42e-42b4-ab17-694030cdf7e2
    resourceVersion: "22529"
    uid: a1a66cf2-a983-4e91-828d-2ef16b94d0fb
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kthcm
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T17:49:37Z"
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.326497ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:49:37Z"
    - latency: 2.19079ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:48:37Z"
    - latency: 1.571126ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:47:37Z"
    - latency: 2.198283ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:46:37Z"
    - latency: 1.758961ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:45:37Z"
    - latency: 1.976914ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:44:37Z"
    - latency: 1.931281ms
      message: 'network-check-target-ip-10-0-143-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:43:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T17:42:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-211-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-211.ec2.internal
      uid: fbf5ff39-d42e-42b4-ab17-694030cdf7e2
    resourceVersion: "21311"
    uid: d63c3003-0450-4f2e-831d-78d889820749
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kthcm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T17:48:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 954.671µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:48:37Z"
    - latency: 1.831233ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:48:37Z"
    - latency: 872.445µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:47:37Z"
    - latency: 1.897974ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:47:37Z"
    - latency: 925.29µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:46:37Z"
    - latency: 2.033955ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:46:37Z"
    - latency: 936.21µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:45:37Z"
    - latency: 1.816397ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:45:37Z"
    - latency: 771.938µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T17:44:37Z"
    - latency: 2.636608ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T17:44:37Z"
kind: List
metadata:
  resourceVersion: ""