Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • v2.28.0
  • v2.27.0
  • v2.25.1
  • v2.24.3
  • v2.26.0
  • v2.24.2
  • v2.25.0
  • v2.24.1
  • v2.22.2
  • v2.23.3
  • v2.24.0
  • v2.23.2
  • v2.23.1
  • v2.23.0
  • v2.22.1
  • v2.22.0
  • v2.21.0
  • v2.20.0
  • v2.19.1
  • v2.18.2
21 results

kubespray

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Max Gautier authored
    This is a followup to 2ba28a33 (Revert "Wait for available API token in
    a new namespace (#7045)", 2024-10-25).
    
    While checking for the serviceaccount token is not effective, there is
    still a race when creating a Pod directly, because the ServiceAccount
    itself might not be created yet.
    More details at https://github.com/kubernetes/kubernetes/issues/66689.
    
    This cause very frequent flakes in our CI with spurious failures.
    
    Use a Deployment instead ; it will takes cares of creating the Pods and
    retrying ; it also let us use kubectl rollout status instead of manually
    checking for the pods.
    930df78d
    History
    Name Last commit Last update