Pin `kubernetes_asyncio` to `29.0.0`

[aktech]

Reference Issues or PRs

A recent release in kubernetes_asyncio has broken JupyterHub and jhub-apps.

Fixes #163

https://github.com/nebari-dev/nebari-docker-images/pull/161 needs to get in first to make the CI work again.

│   File "/opt/conda/lib/python3.9/site-packages/kubernetes_asyncio/config/kube_config.py", line 38, in <module>                                                                                                                                                               │
│     KUBE_CONFIG_DEFAULT_LOCATION = os.environ.get('KUBECONFIG', (pathlib.Path.home() / '.kube/config').as_posix())                                                                                                                                                           │
│   File "/opt/conda/lib/python3.9/pathlib.py", line 1143, in home                                                                                                                                                                                                             │
│     return cls(cls()._flavour.gethomedir(None))                                                                                                                                                                                                                              │
│   File "/opt/conda/lib/python3.9/pathlib.py", line 390, in gethomedir                                                                                                                                                                                                        │
│     return pwd.getpwuid(os.getuid()).pw_dir                                                                                                                                                                                                                                  │
│ KeyError: 'getpwuid(): uid not found: 1000'                                         

It was released on Jun 9, 2024 Pull request in upstream, that potentially caused it: https://github.com/tomplus/kubernetes_asyncio/pull/307

I have verified the error is gone in the previous version.

What does this implement/fix?

Put a x in the boxes that apply

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds a feature)
• [ ] Breaking change (fix or feature that would cause existing features not to work as expected)
• [ ] Documentation Update
• [ ] Code style update (formatting, renaming)
• [ ] Refactoring (no functional changes, no API changes)
• [ ] Build related changes
• [ ] Other (please describe):

Testing

• [x] Did you test the pull request locally?
• [ ] Did you add new tests?

Documentation

Access-centered content checklist

Text styling

• [ ] The content is written with plain language (where relevant).
• [ ] If there are headers, they use the proper header tags (with only one level-one header: H1 or # in markdown).
• [ ] All links describe where they link to (for example, check the Nebari website).
• [ ] This content adheres to the Nebari style guides.

Non-text content

• [ ] All content is represented as text (for example, images need alt text, and videos need captions or descriptive transcripts).
• [ ] If there are emojis, there are not more than three in a row.
• [ ] Don't use flashing GIFs or videos.
• [ ] If the content were to be read as plain text, it still makes sense, and no information is missing.

Any other comments?

[krassowski]

Do we need to report the kubernetes_asyncio issue somewhere upstream so that it is fixed once we do need to migrate?

[aktech]

Do we need to report the kubernetes_asyncio issue somewhere upstream so that it is fixed once we do need to migrate?

I am still looking to see why it happened (with that innocent looking change) but didn't had the chance to create a minimal example (on why that small change affects us) to create an issue on upstream, I'll put up something sometime this week.

[marcelovilla]

@aktech do we need to get this in for the next Nebari release?

[aktech]

@marcelovilla Yes, absolutely, otherwise nebari jhub-apps is broken.