apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:31:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-114-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-114.ec2.internal
      uid: f75a0f6e-f68e-4aec-9a11-b89e7ef57601
    resourceVersion: "22501"
    uid: 515a5f5c-ae34-42d2-a38a-c4b60add797d
  spec:
    sourcePod: network-check-source-56499946bc-tqwkb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:38:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 947.867µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:38:03Z"
    - latency: 1.20103ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:37:03Z"
    - latency: 1.114234ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:36:03Z"
    - latency: 1.328442ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:35:03Z"
    - latency: 1.086029ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:34:03Z"
    - latency: 968.06µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:33:03Z"
    - latency: 1.258779ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:32:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:31:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-114-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-114.ec2.internal
      uid: f75a0f6e-f68e-4aec-9a11-b89e7ef57601
    resourceVersion: "21489"
    uid: 283eaaff-c4ca-4882-b6eb-968cbc7398cd
  spec:
    sourcePod: network-check-source-56499946bc-tqwkb
    targetEndpoint: a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:37:03Z"
      message: 'load-balancer-api-external: tcp connection to a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.230205ms
      message: 'load-balancer-api-external: tcp connection to a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:37:03Z"
    - latency: 12.735563ms
      message: 'load-balancer-api-external: resolved host name a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:37:03Z"
    - latency: 4.932052ms
      message: 'load-balancer-api-external: tcp connection to a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:36:03Z"
    - latency: 10.790624ms
      message: 'load-balancer-api-external: resolved host name a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:36:03Z"
    - latency: 6.091949ms
      message: 'load-balancer-api-external: tcp connection to a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:35:03Z"
    - latency: 8.7995ms
      message: 'load-balancer-api-external: resolved host name a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:35:03Z"
    - latency: 4.041071ms
      message: 'load-balancer-api-external: tcp connection to a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:34:03Z"
    - latency: 10.181475ms
      message: 'load-balancer-api-external: resolved host name a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:34:03Z"
    - latency: 4.716594ms
      message: 'load-balancer-api-external: tcp connection to a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:33:03Z"
    - latency: 8.969815ms
      message: 'load-balancer-api-external: resolved host name a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:33:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:31:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-114-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-114.ec2.internal
      uid: f75a0f6e-f68e-4aec-9a11-b89e7ef57601
    resourceVersion: "21490"
    uid: c39a1b60-e4b7-4971-9e89-b68f512fd2ec
  spec:
    sourcePod: network-check-source-56499946bc-tqwkb
    targetEndpoint: a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:37:03Z"
      message: 'load-balancer-api-internal: tcp connection to a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.24361ms
      message: 'load-balancer-api-internal: tcp connection to a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:37:03Z"
    - latency: 12.66861ms
      message: 'load-balancer-api-internal: resolved host name a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:37:03Z"
    - latency: 4.602851ms
      message: 'load-balancer-api-internal: tcp connection to a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:36:03Z"
    - latency: 10.715293ms
      message: 'load-balancer-api-internal: resolved host name a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:36:03Z"
    - latency: 5.670903ms
      message: 'load-balancer-api-internal: tcp connection to a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:35:03Z"
    - latency: 8.752488ms
      message: 'load-balancer-api-internal: resolved host name a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:35:03Z"
    - latency: 3.867941ms
      message: 'load-balancer-api-internal: tcp connection to a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:34:03Z"
    - latency: 10.093979ms
      message: 'load-balancer-api-internal: resolved host name a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:34:03Z"
    - latency: 4.709912ms
      message: 'load-balancer-api-internal: tcp connection to a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:33:03Z"
    - latency: 8.939857ms
      message: 'load-balancer-api-internal: resolved host name a5c92ee4097c14210b8507cefcc466bf-afeee96bbad470fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:33:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:31:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-114-to-network-check-target-ip-10-0-128-190
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-114.ec2.internal
      uid: f75a0f6e-f68e-4aec-9a11-b89e7ef57601
    resourceVersion: "22499"
    uid: f6bcfff0-4966-4e08-bc7a-2d43c2d4ca36
  spec:
    sourcePod: network-check-source-56499946bc-tqwkb
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:38:03Z"
      message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.002061ms
      message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:38:03Z"
    - latency: 2.10023ms
      message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:37:03Z"
    - latency: 1.901425ms
      message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:36:03Z"
    - latency: 1.94656ms
      message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:35:03Z"
    - latency: 1.870482ms
      message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:34:03Z"
    - latency: 2.153157ms
      message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:33:03Z"
    - latency: 2.154585ms
      message: 'network-check-target-ip-10-0-128-190: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:32:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:31:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-114-to-network-check-target-ip-10-0-133-114
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-114.ec2.internal
      uid: f75a0f6e-f68e-4aec-9a11-b89e7ef57601
    resourceVersion: "22498"
    uid: 9cb9a94b-dbb4-40e7-aff8-483e61de46a0
  spec:
    sourcePod: network-check-source-56499946bc-tqwkb
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:38:03Z"
      message: 'network-check-target-ip-10-0-133-114: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.27082ms
      message: 'network-check-target-ip-10-0-133-114: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:38:03Z"
    - latency: 1.066911ms
      message: 'network-check-target-ip-10-0-133-114: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:37:03Z"
    - latency: 1.078769ms
      message: 'network-check-target-ip-10-0-133-114: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:36:03Z"
    - latency: 743.269µs
      message: 'network-check-target-ip-10-0-133-114: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:35:03Z"
    - latency: 1.352525ms
      message: 'network-check-target-ip-10-0-133-114: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:34:03Z"
    - latency: 919.076µs
      message: 'network-check-target-ip-10-0-133-114: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:33:03Z"
    - latency: 1.079139ms
      message: 'network-check-target-ip-10-0-133-114: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:32:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:31:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-114-to-network-check-target-ip-10-0-135-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-114.ec2.internal
      uid: f75a0f6e-f68e-4aec-9a11-b89e7ef57601
    resourceVersion: "22500"
    uid: 9d258ac8-82da-4e72-b412-1305167474e2
  spec:
    sourcePod: network-check-source-56499946bc-tqwkb
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:38:03Z"
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.338569ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:38:03Z"
    - latency: 2.183217ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:37:03Z"
    - latency: 2.297326ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:36:03Z"
    - latency: 2.342459ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:35:03Z"
    - latency: 2.075471ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:34:03Z"
    - latency: 2.298375ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:33:03Z"
    - latency: 2.366865ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:32:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:31:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-114-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-114.ec2.internal
      uid: f75a0f6e-f68e-4aec-9a11-b89e7ef57601
    resourceVersion: "21488"
    uid: ec6f5bcd-a0b5-4261-841e-3af96a636d5f
  spec:
    sourcePod: network-check-source-56499946bc-tqwkb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:37:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 929.697µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:37:03Z"
    - latency: 2.082113ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:37:03Z"
    - latency: 882.957µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:36:03Z"
    - latency: 1.686307ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:36:03Z"
    - latency: 853.83µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:35:03Z"
    - latency: 1.793974ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:35:03Z"
    - latency: 892.735µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:34:03Z"
    - latency: 1.682297ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:34:03Z"
    - latency: 889.351µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:33:03Z"
    - latency: 1.819539ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:33:03Z"
kind: List
metadata:
  resourceVersion: ""