Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
e7a10120
Commit
e7a10120
authored
Oct 07, 2020
by
Shinya Maeda
Committed by
Nick Gaskill
Oct 07, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Improve documentation for legacy cluster installation
This commit improves the troubleshooting section
parent
aedde12c
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
48 additions
and
0 deletions
+48
-0
doc/topics/autodevops/index.md
doc/topics/autodevops/index.md
+48
-0
No files found.
doc/topics/autodevops/index.md
View file @
e7a10120
...
...
@@ -418,6 +418,54 @@ DANGER: **Danger:**
Setting
`POSTGRES_ENABLED`
to
`false`
permanently deletes any existing
channel 1 database for your environment.
### Error: unable to recognize "": no matches for kind "Deployment" in version "extensions/v1beta1"
After upgrading your Kubernetes cluster to
[
v1.16+
](
stages.md#kubernetes-116
)
,
you may encounter this message when deploying with Auto DevOps:
```
plaintext
UPGRADE FAILED
Error: failed decoding reader into objects: unable to recognize "": no matches for kind "Deployment" in version "extensions/v1beta1"
```
This can occur if your current deployments on the environment namespace were deployed with a
deprecated/removed API that doesn't exist in Kubernetes v1.16+. For example,
if
[
your in-cluster PostgreSQL was installed in a legacy way
](
#detected-an-existing-postgresql-database
)
,
the resource was created via the
`extensions/v1beta1`
API. However, the deployment resource
was moved to the
`app/v1`
API in v1.16.
To recover such outdated resources, you must convert the current deployments by mapping legacy APIs
to newer APIs. There is a helper tool called
[
`mapkubeapis`
](
https://github.com/hickeyma/helm-mapkubeapis
)
that works for this problem. Follow these steps to use the tool in Auto DevOps:
1.
Modify your
`.gitlab-ci.yml`
with:
```
yaml
include
:
-
template
:
Auto-DevOps.gitlab-ci.yml
-
remote
:
https://gitlab.com/shinya.maeda/ci-templates/-/raw/master/map-deprecated-api.gitlab-ci.yml
variables
:
HELM_VERSION_FOR_MAPKUBEAPIS
:
"
v2"
# If you're using auto-depoy-image v2 or above, please specify "v3".
```
1.
Run the job
`<environment-name>:map-deprecated-api`
. Ensure that this job succeeds before moving
to the next step. You should see something like the following output:
```
shell
2020/10/06 07:20:49 Found deprecated or removed Kubernetes API:
"apiVersion: extensions/v1beta1
kind: Deployment"
Supported API equivalent:
"apiVersion: apps/v1
kind: Deployment"
```
1.
Revert your
`.gitlab-ci.yml`
to the previous version. You no longer need to include the
supplemental template
`map-deprecated-api`
.
1.
Continue the deployments as usual.
## Development guides
[
Development guide for Auto DevOps
](
../../development/auto_devops.md
)
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment