apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T14:07:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-204-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-204.ec2.internal
      uid: 35452600-5a1b-4329-8bbd-1e2a2ed0bef1
    resourceVersion: "24714"
    uid: 53842235-0932-43be-8862-fd76db8e3676
  spec:
    sourcePod: network-check-source-56499946bc-895nd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T14:14: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.081924ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:14:50Z"
    - latency: 1.04849ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:13:50Z"
    - latency: 881.257µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:12:50Z"
    - latency: 933.938µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:11:50Z"
    - latency: 960.418µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:10:50Z"
    - latency: 815.514µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:09:50Z"
    - latency: 2.297228ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:08:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T14:07:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-204-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-204.ec2.internal
      uid: 35452600-5a1b-4329-8bbd-1e2a2ed0bef1
    resourceVersion: "23482"
    uid: 0d69ee9c-4058-4b29-8d30-ea22b945e02e
  spec:
    sourcePod: network-check-source-56499946bc-895nd
    targetEndpoint: a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T14:13:50Z"
      message: 'load-balancer-api-external: tcp connection to a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.217017ms
      message: 'load-balancer-api-external: tcp connection to a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:13:50Z"
    - latency: 8.871287ms
      message: 'load-balancer-api-external: resolved host name a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:13:50Z"
    - latency: 4.813883ms
      message: 'load-balancer-api-external: tcp connection to a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:12:50Z"
    - latency: 8.368235ms
      message: 'load-balancer-api-external: resolved host name a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:12:50Z"
    - latency: 5.316191ms
      message: 'load-balancer-api-external: tcp connection to a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:11:50Z"
    - latency: 8.801206ms
      message: 'load-balancer-api-external: resolved host name a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:11:50Z"
    - latency: 4.796221ms
      message: 'load-balancer-api-external: tcp connection to a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:10:50Z"
    - latency: 8.110273ms
      message: 'load-balancer-api-external: resolved host name a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:10:50Z"
    - latency: 5.026224ms
      message: 'load-balancer-api-external: tcp connection to a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:09:50Z"
    - latency: 8.849363ms
      message: 'load-balancer-api-external: resolved host name a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:09:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T14:07:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-204-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-204.ec2.internal
      uid: 35452600-5a1b-4329-8bbd-1e2a2ed0bef1
    resourceVersion: "23481"
    uid: c78e566c-750e-4dcc-9a53-9769e37e6168
  spec:
    sourcePod: network-check-source-56499946bc-895nd
    targetEndpoint: a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T14:13:50Z"
      message: 'load-balancer-api-internal: tcp connection to a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.290081ms
      message: 'load-balancer-api-internal: tcp connection to a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:13:50Z"
    - latency: 8.827892ms
      message: 'load-balancer-api-internal: resolved host name a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:13:50Z"
    - latency: 4.578016ms
      message: 'load-balancer-api-internal: tcp connection to a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:12:50Z"
    - latency: 8.195236ms
      message: 'load-balancer-api-internal: resolved host name a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:12:50Z"
    - latency: 4.736094ms
      message: 'load-balancer-api-internal: tcp connection to a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:11:50Z"
    - latency: 8.765178ms
      message: 'load-balancer-api-internal: resolved host name a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:11:50Z"
    - latency: 4.795193ms
      message: 'load-balancer-api-internal: tcp connection to a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:10:50Z"
    - latency: 8.083983ms
      message: 'load-balancer-api-internal: resolved host name a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:10:50Z"
    - latency: 5.040987ms
      message: 'load-balancer-api-internal: tcp connection to a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:09:50Z"
    - latency: 8.78459ms
      message: 'load-balancer-api-internal: resolved host name a71cb60ec7f39447db81274ca020e1c8-8ed91803f3291e09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:09:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T14:07:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-204-to-network-check-target-ip-10-0-132-214
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-204.ec2.internal
      uid: 35452600-5a1b-4329-8bbd-1e2a2ed0bef1
    resourceVersion: "24711"
    uid: 9418d946-c18c-46b2-852e-635ca088014a
  spec:
    sourcePod: network-check-source-56499946bc-895nd
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T14:14:50Z"
      message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.166545ms
      message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:14:50Z"
    - latency: 2.216156ms
      message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:13:50Z"
    - latency: 2.479853ms
      message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:12:50Z"
    - latency: 2.009622ms
      message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:11:50Z"
    - latency: 2.318102ms
      message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:10:50Z"
    - latency: 2.161178ms
      message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:09:50Z"
    - latency: 2.703512ms
      message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:08:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T14:07:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-204-to-network-check-target-ip-10-0-133-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-204.ec2.internal
      uid: 35452600-5a1b-4329-8bbd-1e2a2ed0bef1
    resourceVersion: "24712"
    uid: 09cd3437-44b3-41c2-84b6-06ec7a0b01c3
  spec:
    sourcePod: network-check-source-56499946bc-895nd
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T14:14:50Z"
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.248154ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:14:50Z"
    - latency: 2.35697ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:13:50Z"
    - latency: 2.045281ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:12:50Z"
    - latency: 2.291283ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:11:50Z"
    - latency: 2.249456ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:10:50Z"
    - latency: 2.353299ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:09:50Z"
    - latency: 2.666382ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:08:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T14:07:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-204-to-network-check-target-ip-10-0-137-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-204.ec2.internal
      uid: 35452600-5a1b-4329-8bbd-1e2a2ed0bef1
    resourceVersion: "24713"
    uid: 59851e98-50a0-4730-ab10-ab9577b37a49
  spec:
    sourcePod: network-check-source-56499946bc-895nd
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T14:14:50Z"
      message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 887.009µs
      message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:14:50Z"
    - latency: 891.36µs
      message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:13:50Z"
    - latency: 1.181701ms
      message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:12:50Z"
    - latency: 821.966µs
      message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:11:50Z"
    - latency: 1.082392ms
      message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:10:50Z"
    - latency: 963.73µs
      message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:09:50Z"
    - latency: 1.297607ms
      message: 'network-check-target-ip-10-0-137-204: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:08:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T14:07:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-204-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-204.ec2.internal
      uid: 35452600-5a1b-4329-8bbd-1e2a2ed0bef1
    resourceVersion: "23476"
    uid: 502aaa70-6ebb-4a7c-aea9-81ba94a18889
  spec:
    sourcePod: network-check-source-56499946bc-895nd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T14:13:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.091432ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:13:50Z"
    - latency: 1.762643ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:13:50Z"
    - latency: 1.150053ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:12:50Z"
    - latency: 1.782705ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:12:50Z"
    - latency: 1.327781ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:11:50Z"
    - latency: 1.59116ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:11:50Z"
    - latency: 799.682µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:10:50Z"
    - latency: 1.480199ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:10:50Z"
    - latency: 786.883µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:09:50Z"
    - latency: 1.503234ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:09:50Z"
kind: List
metadata:
  resourceVersion: ""