apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T16:25:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-252-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-252.us-west-2.compute.internal
      uid: 976a77a1-6597-4668-9169-f0d5ea8ae780
    resourceVersion: "19740"
    uid: 26858e6f-8590-4f0f-acdf-b9b821737c1f
  spec:
    sourcePod: network-check-source-6f78d59f99-4bskr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T16:32:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 868.942µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:32:51Z"
    - latency: 1.134403ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:31:51Z"
    - latency: 1.270844ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:30:51Z"
    - latency: 887.826µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:29:51Z"
    - latency: 980.179µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:28:51Z"
    - latency: 753.38µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:27:51Z"
    - latency: 1.170997ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:26:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T16:25:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-252-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-252.us-west-2.compute.internal
      uid: 976a77a1-6597-4668-9169-f0d5ea8ae780
    resourceVersion: "19741"
    uid: 76ea8d9b-6d06-483f-9e99-0cf1070fb556
  spec:
    sourcePod: network-check-source-6f78d59f99-4bskr
    targetEndpoint: acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T16:32:51Z"
      message: 'load-balancer-api-external: tcp connection to acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 57.737352ms
      message: 'load-balancer-api-external: tcp connection to acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:32:51Z"
    - latency: 6.727498ms
      message: 'load-balancer-api-external: resolved host name acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:32:51Z"
    - latency: 51.373329ms
      message: 'load-balancer-api-external: tcp connection to acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:31:51Z"
    - latency: 5.978897ms
      message: 'load-balancer-api-external: resolved host name acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:31:51Z"
    - latency: 55.886089ms
      message: 'load-balancer-api-external: tcp connection to acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:30:51Z"
    - latency: 7.360996ms
      message: 'load-balancer-api-external: resolved host name acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:30:51Z"
    - latency: 53.799462ms
      message: 'load-balancer-api-external: tcp connection to acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:29:51Z"
    - latency: 9.59547ms
      message: 'load-balancer-api-external: resolved host name acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:29:51Z"
    - latency: 49.816959ms
      message: 'load-balancer-api-external: tcp connection to acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:28:51Z"
    - latency: 8.096166ms
      message: 'load-balancer-api-external: resolved host name acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:28:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T16:25:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-252-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-252.us-west-2.compute.internal
      uid: 976a77a1-6597-4668-9169-f0d5ea8ae780
    resourceVersion: "19058"
    uid: 2a450b03-cfa2-46fe-88b1-e6b92030fdd0
  spec:
    sourcePod: network-check-source-6f78d59f99-4bskr
    targetEndpoint: acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T16:31:51Z"
      message: 'load-balancer-api-internal: tcp connection to acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 55.059396ms
      message: 'load-balancer-api-internal: tcp connection to acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:31:51Z"
    - latency: 5.953276ms
      message: 'load-balancer-api-internal: resolved host name acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:31:51Z"
    - latency: 54.903958ms
      message: 'load-balancer-api-internal: tcp connection to acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:30:51Z"
    - latency: 7.442985ms
      message: 'load-balancer-api-internal: resolved host name acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:30:51Z"
    - latency: 49.966988ms
      message: 'load-balancer-api-internal: tcp connection to acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:29:51Z"
    - latency: 9.69341ms
      message: 'load-balancer-api-internal: resolved host name acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:29:51Z"
    - latency: 49.366626ms
      message: 'load-balancer-api-internal: tcp connection to acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:28:51Z"
    - latency: 8.168965ms
      message: 'load-balancer-api-internal: resolved host name acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:28:51Z"
    - latency: 52.144669ms
      message: 'load-balancer-api-internal: tcp connection to acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:27:51Z"
    - latency: 7.379107ms
      message: 'load-balancer-api-internal: resolved host name acf881a094c69491da08ab1d13ccb3df-44ae1f8e4fa86960.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:27:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T16:25:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-252-to-network-check-target-ip-10-0-133-252
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-252.us-west-2.compute.internal
      uid: 976a77a1-6597-4668-9169-f0d5ea8ae780
    resourceVersion: "19736"
    uid: 588004ba-bd7a-4c39-8667-d2fa874f56c4
  spec:
    sourcePod: network-check-source-6f78d59f99-4bskr
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T16:32:51Z"
      message: 'network-check-target-ip-10-0-133-252: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 811.548µs
      message: 'network-check-target-ip-10-0-133-252: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:32:51Z"
    - latency: 760.666µs
      message: 'network-check-target-ip-10-0-133-252: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:31:51Z"
    - latency: 994.639µs
      message: 'network-check-target-ip-10-0-133-252: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:30:51Z"
    - latency: 841.941µs
      message: 'network-check-target-ip-10-0-133-252: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:29:51Z"
    - latency: 1.004623ms
      message: 'network-check-target-ip-10-0-133-252: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:28:51Z"
    - latency: 792.693µs
      message: 'network-check-target-ip-10-0-133-252: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:27:51Z"
    - latency: 1.228449ms
      message: 'network-check-target-ip-10-0-133-252: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:26:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T16:25:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-252-to-network-check-target-ip-10-0-137-117
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-252.us-west-2.compute.internal
      uid: 976a77a1-6597-4668-9169-f0d5ea8ae780
    resourceVersion: "19738"
    uid: 78729e38-5427-4712-8912-d0f6c20053a3
  spec:
    sourcePod: network-check-source-6f78d59f99-4bskr
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T16:32:51Z"
      message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.204953ms
      message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:32:51Z"
    - latency: 2.291806ms
      message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:31:51Z"
    - latency: 2.22535ms
      message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:30:51Z"
    - latency: 2.196193ms
      message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:29:51Z"
    - latency: 2.26398ms
      message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:28:51Z"
    - latency: 2.247025ms
      message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:27:51Z"
    - latency: 2.363467ms
      message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:26:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T16:25:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-252-to-network-check-target-ip-10-0-139-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-252.us-west-2.compute.internal
      uid: 976a77a1-6597-4668-9169-f0d5ea8ae780
    resourceVersion: "19737"
    uid: 10baf0a6-59b7-42d0-b3b5-d8e8779d77b7
  spec:
    sourcePod: network-check-source-6f78d59f99-4bskr
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T16:32:51Z"
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.593307ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:32:51Z"
    - latency: 1.960362ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:31:51Z"
    - latency: 1.893286ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:30:51Z"
    - latency: 1.785288ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:29:51Z"
    - latency: 1.960997ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:28:51Z"
    - latency: 1.767499ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:27:51Z"
    - latency: 1.931704ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:26:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T16:25:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-252-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-252.us-west-2.compute.internal
      uid: 976a77a1-6597-4668-9169-f0d5ea8ae780
    resourceVersion: "19056"
    uid: f9fb58d6-b16d-419f-be92-9f832b8d84a1
  spec:
    sourcePod: network-check-source-6f78d59f99-4bskr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T16:31:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 771.154µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:31:51Z"
    - latency: 1.735747ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:31:51Z"
    - latency: 1.104128ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:30:51Z"
    - latency: 1.661062ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:30:51Z"
    - latency: 861.279µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:29:51Z"
    - latency: 2.119235ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:29:51Z"
    - latency: 1.137439ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:28:51Z"
    - latency: 1.755855ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:28:51Z"
    - latency: 836.134µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:27:51Z"
    - latency: 1.611609ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:27:51Z"
kind: List
metadata:
  resourceVersion: ""