Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Empty file added index.json
Empty file.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
73 changes: 73 additions & 0 deletions src/en/guides/account-management/kubernetes/credentials.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,11 +18,16 @@ In order to integrate a vendor-managed Kubernetes cluster into our system, you c
Supported Credential Types include:
- [AWS](#aws)
- [Azure](#azure)
- [Azure Storage](#azure-storage)
- [Cloudflare R2 Storage](#cloudflare-r2-storage)
- [Digital Ocean](#digital-ocean)
- [Google Cloud](#google-cloud)
- [Google OAuth](#google-oauth)
- [Hetzner](#hetzner)
- [Linode](#linode)
- [Rancher](#rancher)
- [Scaleway](#scaleway)
- [Vultr](#vultr)

Visit https://home.appscode.com/user/settings/credentials to manage credential.

Expand Down Expand Up @@ -365,3 +370,71 @@ Reference: [Rancher API Keys](https://ranchermanager.docs.rancher.com/reference-
Copy the generated access key, secret key, and API endpoint from the `Account & API Keys` overview page.

Next, add these credentials to the [AppsCode user settings credentials page](https://home.appscode.com/user/settings/credentials/create).

<img align="right" width="50%" src="../images/credentials/azureStorage.png">

## Azure Storage

To access Azure Blob Storage, you need your Storage Account name and one of its access keys.

- **Account:** Your Storage Account name, found in the Azure Portal under **Storage accounts**.
- **Key:** One of the access keys (key1 or key2), found under **Security + networking > Access keys** in the storage account sidebar. Click **Show** to reveal the key value.

Then add the credential [here](https://home.appscode.com/user/settings/credentials/create).

<br><br><br><br>

<img align="right" width="50%" src="../images/credentials/cloudflareStorage.png">

## Cloudflare R2 Storage

To access Cloudflare R2 Object Storage, you need your Account ID and an R2 API token.

- **Account ID:** Found on your Cloudflare Dashboard under **R2 > Overview** or in the sidebar.
- **Access Key ID & Secret Access Key:** Generated by creating an R2 API token. Navigate to **R2 > Manage R2 API Tokens > Create API Token** and ensure the token has `Edit` permissions for the target bucket.

Then add the credential [here](https://home.appscode.com/user/settings/credentials/create).

<br><br><br><br>

<img align="right" width="50%" src="../images/credentials/Hetzner.png">

## Hetzner

To access Hetzner Cloud resources, you need an API token and an SSH key.

- **SSH Key Name:** The name of an existing SSH key registered in your Hetzner Cloud project.
- **Token:** A Hetzner Cloud API token. Generate one under **Security > API Tokens** in your Hetzner Cloud Console. Use `Read & Write` permissions.

Ref: [Hetzner Cloud API Tokens](https://docs.hetzner.com/cloud/api/getting-started/generating-api-token/)

Then add the credential [here](https://home.appscode.com/user/settings/credentials/create).

<br><br><br>

<img align="right" width="50%" src="../images/credentials/Scaleway.png">

## Scaleway

To access Scaleway resources, you need your Organization ID and an API secret key.

- **Organization:** Your Scaleway Organization ID (a UUID), found under **Organization Settings** in the Scaleway Console.
- **Token:** Your API Secret Key. Navigate to **Identity and Access Management (IAM) > API Keys**, create a new API key, and copy the **Secret Key**.

Ref: [Scaleway API Keys](https://www.scaleway.com/en/docs/iam/api-keys/)

Then add the credential [here](https://home.appscode.com/user/settings/credentials/create).

<br><br><br>

<img align="right" width="50%" src="../images/credentials/vultr.png">

## Vultr

To access Vultr resources, you need a Vultr API key.

- **Token:** Your Vultr API key. Navigate to **Account > API** in the Vultr customer portal and generate a personal access token.

Ref: [Vultr API](https://www.vultr.com/api/)

Then add the credential [here](https://home.appscode.com/user/settings/credentials/create).
Original file line number Diff line number Diff line change
@@ -0,0 +1,67 @@
---
layout: 'guide'
menu:
v2_1_0_docs_menu:
identifier: account-management-siteadmin-ace-upgrade
name: ACE Upgrade
parent: account-management-siteadmin
weight: 60
menu_name: v2_1_0_docs_menu
section_menu: guides
---


# ACE Upgrade

Site administrators can upgrade the AppsCode Enterprise (ACE) management cluster directly from the platform UI by uploading a configuration file downloaded from the AppsCode portal.

---

## Prerequisites

Before starting the upgrade, download the required values file from the AppsCode portal:

1. Log in to [appscode.com](https://appscode.com) and switch to your organization.
2. Locate the installer currently in use and click **View Details**, then select **Upgrade**.
3. Click **Download** to save the archive to your local machine. It contains the `values.yaml` file needed for the upgrade.

---

## Step 1 — Open ACE Upgrade

![ACE Version Page](../images/upgrade-version-1.png)

Go to **SITE ADMINISTRATION > ACE Upgrade** from the left-hand menu.

The page displays the current ACE version and the upgrade status of all platform components. Click the **Upgrade Version** button at the top right to begin.

---

## Step 2 — Upload the Values File

![Upload Values File](../images/upgrade-version-2.png)

On the **Upgrade ACE** screen:

- Click **Upload values file...** and select the `values.yaml` file downloaded from the AppsCode portal.
- Click **Update Version** to start the upgrade process.

---

## Step 3 — Monitor Upgrade Progress

![Upgrade In Progress](../images/upgrade-version-3.png)

The platform will upgrade individual components one by one. You can track progress directly on this page:

- Components currently being updated show a **refresh icon**.
- Completed components show a **green checkmark**.
- The overall status displays as **Progressing** while the upgrade is running.

---

## Step 4 — Verify Completion

![Upgrade Complete](../images/upgrade-version-4.png)

Once all components have been updated, the status changes to **Updated**. Confirm that the new version number is correctly reflected at the top of the page.
Loading