Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[GSoC2024] update helm documentation for creating superuser #7631

Merged
merged 1 commit into from
Mar 26, 2024

Conversation

abhi-bhatra
Copy link
Contributor

@abhi-bhatra abhi-bhatra commented Mar 18, 2024

Motivation and context

**Issue: ** #7605
Currently, the command used in the official documentation is not working, and giving error:

  1. Command Used:
BACKEND_POD_NAME=$(kubectl get pod --namespace $HELM_RELEASE_NAMESPACE -l tier=backend,app.kubernetes.io/instance=$HELM_RELEASE_NAME -o jsonpath='{.items[0].metadata.name}') &&\
kubectl exec -it --namespace $HELM_RELEASE_NAMESPACE $BACKEND_POD_NAME -c cvat-backend-app-container -- python manage.py createsuperuser
  1. Actual Output:
    image

  2. Expected Output:
    image

How has this been tested?

I have run a minikube cluster, and run the as it is command in cluster, which gives error:

error: cannot exec into a container in a completed pod; current phase is Succeeded

Checklist

  • I submit my changes into the develop branch
  • I have created a changelog fragment
  • I have updated the documentation accordingly
  • I have added tests to cover my changes
  • I have linked related issues (see GitHub docs)
  • I have increased versions of npm packages if it is necessary
    (cvat-canvas,
    cvat-core,
    cvat-data and
    cvat-ui)

License

  • I submit my code changes under the same MIT License that covers the project.
    Feel free to contact the maintainers if that's a concern.

@abhi-bhatra abhi-bhatra requested a review from mdacoca as a code owner March 18, 2024 08:09
@nmanovic nmanovic changed the title update helm documentation for creating superuser [GSoC2024] update helm documentation for creating superuser Mar 22, 2024
@nmanovic nmanovic requested review from azhavoro and removed request for mdacoca March 22, 2024 14:58
@nmanovic
Copy link
Contributor

@azhavoro , do you have any comments?

@azhavoro azhavoro merged commit 7533496 into cvat-ai:develop Mar 26, 2024
13 checks passed
g-kartik pushed a commit to g-kartik/cvat that referenced this pull request Mar 29, 2024
…7631)

<!-- Raise an issue to propose your change
(https://github.com/opencv/cvat/issues).
It helps to avoid duplication of efforts from multiple independent
contributors.
Discuss your ideas with maintainers to be sure that changes will be
approved and merged.
Read the [Contribution
guide](https://opencv.github.io/cvat/docs/contributing/). -->

<!-- Provide a general summary of your changes in the Title above -->

### Motivation and context
<!-- Why is this change required? What problem does it solve? If it
fixes an open
issue, please link to the issue here. Describe your changes in detail,
add
screenshots. -->

**Issue: ** cvat-ai#7605 
Currently, the command used in the official documentation is not
working, and giving error:
1. **Command Used**: 
```shell
BACKEND_POD_NAME=$(kubectl get pod --namespace $HELM_RELEASE_NAMESPACE -l tier=backend,app.kubernetes.io/instance=$HELM_RELEASE_NAME -o jsonpath='{.items[0].metadata.name}') &&\
kubectl exec -it --namespace $HELM_RELEASE_NAMESPACE $BACKEND_POD_NAME -c cvat-backend-app-container -- python manage.py createsuperuser
```

2. **Actual Output**:

![image](https://github.com/opencv/cvat/assets/63901956/bd826a8a-aacb-48e1-8501-04a9c730fa86)

3. **Expected Output**: 

![image](https://github.com/opencv/cvat/assets/63901956/20a31418-3136-46bc-a04d-3c17e44dcbde)


### How has this been tested?
<!-- Please describe in detail how you tested your changes.
Include details of your testing environment, and the tests you ran to
see how your change affects other areas of the code, etc. -->
I have run a minikube cluster, and run the as it is command in cluster,
which gives error:
```shell
error: cannot exec into a container in a completed pod; current phase is Succeeded
```

### Checklist
<!-- Go over all the following points, and put an `x` in all the boxes
that apply.
If an item isn't applicable for some reason, then ~~explicitly
strikethrough~~ the whole
line. If you don't do that, GitHub will show incorrect progress for the
pull request.
If you're unsure about any of these, don't hesitate to ask. We're here
to help! -->
- [x] I submit my changes into the `develop` branch
- [x] I have created a changelog fragment <!-- see top comment in
CHANGELOG.md -->
- [x] I have updated the documentation accordingly
- [x] I have added tests to cover my changes
- [x] I have linked related issues (see [GitHub docs](

https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))
- [x] I have increased versions of npm packages if it is necessary

([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning),

[cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning),

[cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning)
and

[cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning))

### License

- [x] I submit _my code changes_ under the same [MIT License](
https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the
project.
  Feel free to contact the maintainers if that's a concern.

Co-authored-by: abhinav.sharma <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants