apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T21:47:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-212-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-212.ec2.internal
      uid: a4326749-f7d7-49bb-8086-9d03b2e03509
    resourceVersion: "22823"
    uid: 688f2801-4ef2-485b-acb5-ced8c678617a
  spec:
    sourcePod: network-check-source-869dcfcdcd-cxjrq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T21:54:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.257699ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:54:50Z"
    - latency: 1.023855ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:53:50Z"
    - latency: 882.939µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:52:50Z"
    - latency: 1.167757ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:51:50Z"
    - latency: 1.203088ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:50:50Z"
    - latency: 1.322215ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:49:50Z"
    - latency: 1.32293ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:48:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T21:47:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-212-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-212.ec2.internal
      uid: a4326749-f7d7-49bb-8086-9d03b2e03509
    resourceVersion: "27348"
    uid: 4eaef75f-c51c-4528-87d6-4dd82fcd4ded
  spec:
    sourcePod: network-check-source-869dcfcdcd-cxjrq
    targetEndpoint: a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T21:53:50Z"
      message: 'load-balancer-api-external: tcp connection to a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.405936ms
      message: 'load-balancer-api-external: tcp connection to a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:59:50Z"
    - latency: 8.119103ms
      message: 'load-balancer-api-external: resolved host name a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T21:59:50Z"
    - latency: 4.180585ms
      message: 'load-balancer-api-external: tcp connection to a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:58:50Z"
    - latency: 14.308937ms
      message: 'load-balancer-api-external: resolved host name a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T21:58:50Z"
    - latency: 4.710717ms
      message: 'load-balancer-api-external: tcp connection to a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:57:50Z"
    - latency: 8.04905ms
      message: 'load-balancer-api-external: resolved host name a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T21:57:50Z"
    - latency: 5.386097ms
      message: 'load-balancer-api-external: tcp connection to a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:56:50Z"
    - latency: 8.247603ms
      message: 'load-balancer-api-external: resolved host name a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T21:56:50Z"
    - latency: 4.31444ms
      message: 'load-balancer-api-external: tcp connection to a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:55:50Z"
    - latency: 8.100912ms
      message: 'load-balancer-api-external: resolved host name a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T21:55:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T21:47:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-212-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-212.ec2.internal
      uid: a4326749-f7d7-49bb-8086-9d03b2e03509
    resourceVersion: "27349"
    uid: be3edb36-a71a-4dd6-94b5-414094a6f77c
  spec:
    sourcePod: network-check-source-869dcfcdcd-cxjrq
    targetEndpoint: a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T21:53:50Z"
      message: 'load-balancer-api-internal: tcp connection to a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.462373ms
      message: 'load-balancer-api-internal: tcp connection to a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:59:50Z"
    - latency: 8.176667ms
      message: 'load-balancer-api-internal: resolved host name a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T21:59:50Z"
    - latency: 3.952188ms
      message: 'load-balancer-api-internal: tcp connection to a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:58:50Z"
    - latency: 14.033603ms
      message: 'load-balancer-api-internal: resolved host name a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T21:58:50Z"
    - latency: 4.675424ms
      message: 'load-balancer-api-internal: tcp connection to a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:57:50Z"
    - latency: 8.138726ms
      message: 'load-balancer-api-internal: resolved host name a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T21:57:50Z"
    - latency: 5.361547ms
      message: 'load-balancer-api-internal: tcp connection to a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:56:50Z"
    - latency: 8.336932ms
      message: 'load-balancer-api-internal: resolved host name a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T21:56:50Z"
    - latency: 4.361983ms
      message: 'load-balancer-api-internal: tcp connection to a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:55:50Z"
    - latency: 7.962328ms
      message: 'load-balancer-api-internal: resolved host name a5a798b2565f24df091b19e6ba7f5749-1920a5da4be110c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T21:55:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T21:47:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-212-to-network-check-target-ip-10-0-128-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-212.ec2.internal
      uid: a4326749-f7d7-49bb-8086-9d03b2e03509
    resourceVersion: "22822"
    uid: a7389fd6-7650-4567-a080-06cab7174980
  spec:
    sourcePod: network-check-source-869dcfcdcd-cxjrq
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T21:54:50Z"
      message: 'network-check-target-ip-10-0-128-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.014873ms
      message: 'network-check-target-ip-10-0-128-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:54:50Z"
    - latency: 2.4841ms
      message: 'network-check-target-ip-10-0-128-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:53:50Z"
    - latency: 2.602788ms
      message: 'network-check-target-ip-10-0-128-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:52:50Z"
    - latency: 2.200889ms
      message: 'network-check-target-ip-10-0-128-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:51:50Z"
    - latency: 2.167599ms
      message: 'network-check-target-ip-10-0-128-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:50:50Z"
    - latency: 2.149371ms
      message: 'network-check-target-ip-10-0-128-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:49:50Z"
    - latency: 2.779388ms
      message: 'network-check-target-ip-10-0-128-127: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:48:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T21:47:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-212-to-network-check-target-ip-10-0-132-137
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-212.ec2.internal
      uid: a4326749-f7d7-49bb-8086-9d03b2e03509
    resourceVersion: "22820"
    uid: 53d18476-6dce-4f09-be11-81a56a6b92bd
  spec:
    sourcePod: network-check-source-869dcfcdcd-cxjrq
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T21:54:50Z"
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.97781ms
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:54:50Z"
    - latency: 2.29433ms
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:53:50Z"
    - latency: 1.92614ms
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:52:50Z"
    - latency: 2.292474ms
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:51:50Z"
    - latency: 1.697797ms
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:50:50Z"
    - latency: 2.023906ms
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:49:50Z"
    - latency: 2.015886ms
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:48:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T21:47:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-212-to-network-check-target-ip-10-0-137-212
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-212.ec2.internal
      uid: a4326749-f7d7-49bb-8086-9d03b2e03509
    resourceVersion: "22821"
    uid: 70c05cf3-85ed-460f-956f-fd2785e42c1d
  spec:
    sourcePod: network-check-source-869dcfcdcd-cxjrq
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T21:54:50Z"
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.4909ms
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:54:50Z"
    - latency: 766.834µs
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:53:50Z"
    - latency: 968.049µs
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:52:50Z"
    - latency: 1.356374ms
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:51:50Z"
    - latency: 838.193µs
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:50:50Z"
    - latency: 791.119µs
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:49:50Z"
    - latency: 1.152083ms
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:48:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T21:47:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-212-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-212.ec2.internal
      uid: a4326749-f7d7-49bb-8086-9d03b2e03509
    resourceVersion: "27347"
    uid: cfe1d8bb-75b3-47ad-a115-a6099493bf67
  spec:
    sourcePod: network-check-source-869dcfcdcd-cxjrq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T21:53:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 833.135µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:59:50Z"
    - latency: 1.873965ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T21:59:50Z"
    - latency: 891.526µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:58:50Z"
    - latency: 3.007441ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T21:58:50Z"
    - latency: 1.079877ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:57:50Z"
    - latency: 1.857871ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T21:57:50Z"
    - latency: 1.122045ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:56:50Z"
    - latency: 1.630509ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T21:56:50Z"
    - latency: 941.881µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T21:55:50Z"
    - latency: 1.986756ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T21:55:50Z"
kind: List
metadata:
  resourceVersion: ""