diff --git a/.github/workflows/gh-pages.yml b/.github/workflows/gh-pages.yml index c32dacd..88e7415 100644 --- a/.github/workflows/gh-pages.yml +++ b/.github/workflows/gh-pages.yml @@ -9,6 +9,7 @@ on: jobs: deploy: runs-on: ubuntu-20.04 + permissions: write-all concurrency: group: ${{ github.workflow }}-${{ github.ref }} steps: @@ -28,4 +29,4 @@ jobs: with: github_token: ${{ secrets.GITHUB_TOKEN }} publish_dir: ./public - cname: artemiscloud.io + cname: arkmq.org diff --git a/README.md b/README.md index e299b0a..b75dfab 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,4 @@ -# ArtemisCloud.io website +# ArkMQ website ## Requirements @@ -8,7 +8,7 @@
Why Node.js? -ArtemisCloud.io website uses Doks starter theme that uses npm (included with Node.js) to centralize dependency management, making it [easy to update](https://getdoks.org/docs/help/how-to-update/) resources, build tooling, plugins, and build scripts. +ArkMQ website uses Doks starter theme that uses npm (included with Node.js) to centralize dependency management, making it [easy to update](https://getdoks.org/docs/help/how-to-update/) resources, build tooling, plugins, and build scripts.
@@ -19,7 +19,7 @@ Start developing in three steps: ### 1. Clone this repository ```bash -git clone https://github.com/artemiscloud/artemiscloud.github.io.git artemiscloud.github.io.git && cd artemiscloud.github.io.git +git clone https://github.com/arkmq-org/arkmq-org.github.io.git arkmq.github.io.git && cd arkmq.github.io.git ``` ### 2. Install dependencies diff --git a/config/_default/menus/menus.en.toml b/config/_default/menus/menus.en.toml index f47d4e5..3fb61c2 100644 --- a/config/_default/menus/menus.en.toml +++ b/config/_default/menus/menus.en.toml @@ -64,14 +64,14 @@ [[social]] name = "GitHub" pre = "" - url = "https://github.com/artemiscloud" + url = "https://github.com/arkmq-org" post = "v0.1.0" weight = 10 [[social]] name = "Twitter" pre = "" - url = "https://twitter.com/artemiscloudio" + url = "https://twitter.com/arkmq_org" weight = 20 # [[footer]] diff --git a/config/_default/params.toml b/config/_default/params.toml index fdd862a..bfd4573 100644 --- a/config/_default/params.toml +++ b/config/_default/params.toml @@ -1,37 +1,37 @@ # Meta Data for SEO ## Homepage -title = "ArtemisCloud.io" +title = "ArkMQ" titleSeparator = "-" titleAddition = "ActiveMQ Artemis on Kubernetes" -description = "ArtemisCloud.io is a collection of container images that provide a way to deploy the Apache ActiveMQ Artemis Broker on Kubernetes." +description = "ArkMQ is a collection of container images that provide a way to deploy the Apache ActiveMQ Artemis Broker on Kubernetes." ## Documentation # docsVersion = "0.3" ## Open Graph -images = ["artemiscloud.png"] +images = ["arkmq.png"] ogLocale = "en_US" -titleHome = "ArtemisCloud.io" +titleHome = "ArkMQ" ## Twitter Cards -twitterSite = "@artemiscloudio" +twitterSite = "@arkmq_org" twitterCreator = "@henkverlinde" ## JSON-LD # schemaType = "Person" schemaType = "Organization" -schemaName = "ArtemisCloud.io" +schemaName = "ArkMQ" schemaLocale = "en-US" -schemaLogo = "artemiscloud.png" +schemaLogo = "arkmq.png" schemaLogoWidth = 512 schemaLogoHeight = 512 -schemaImage = "artemiscloud.png" +schemaImage = "arkmq.png" schemaImageWidth = 1280 schemaImageHeight = 640 -schemaTwitter = "https://twitter.com/artemiscloudio" +schemaTwitter = "https://twitter.com/arkmq_org" schemaLinkedIn = "" -schemaGitHub = "https://github.com/artemiscloud" +schemaGitHub = "https://github.com/arkmq-org" schemaSection = "blog" ## Sitelinks Search Box @@ -57,12 +57,12 @@ copyRight = "Copyright (c) 2020-2021 Henk Verlinde" # Alert alert = false alertDismissable = true -alertText = "Introducing the ArtemisCloud.io! Check out ArtemisCloud.io" +alertText = "Introducing the ArkMQ! Check out ArkMQ" # Edit Page # repoHost [Github | Gitea | GitLab | Bitbucket | BitbucketServer ] is used for building the edit link based on git hoster repoHost = "GitHub" -docsRepo = "https://github.com/artemiscloud/artemiscloud.github.io" +docsRepo = "https://github.com/arkmq-org/arkmq-org.github.io" docsRepoBranch = "master" docsRepoSubPath = "" editPage = false diff --git a/content/en/_index.md b/content/en/_index.md index 5cf5aec..f90489f 100644 --- a/content/en/_index.md +++ b/content/en/_index.md @@ -1,8 +1,8 @@ --- -title : "ArtemisCloud.io" -description: "ArtemisCloud.io is a collection of container images that provide a way to deploy the Apache ActiveMQ Artemis Broker on Kubernetes." +title : "ArkMQ" +description: "ArkMQ is a collection of container images that provide a way to deploy the Apache ActiveMQ Artemis Broker on Kubernetes." subtitle: "ActiveMQ Artemis on Kubernetes" -lead: "ArtemisCloud.io is a collection of container images that provide a way to deploy the Apache ActiveMQ Artemis Broker on Kubernetes." +lead: "ArkMQ is a collection of container images that provide a way to deploy the Apache ActiveMQ Artemis Broker on Kubernetes." date: 2020-10-06T08:47:36+00:00 lastmod: 2020-10-06T08:47:36+00:00 draft: false diff --git a/content/en/blog/_index.md b/content/en/blog/_index.md index 83d6dc5..579fa5f 100644 --- a/content/en/blog/_index.md +++ b/content/en/blog/_index.md @@ -1,6 +1,6 @@ --- title: "Blog" -description: "The ArtemisCloud Blog." +description: "The ArkMQ Blog." date: 2020-10-06T08:49:55+00:00 lastmod: 2020-10-06T08:49:55+00:00 draft: false diff --git a/content/en/blog/say-hello-to-akrmq/index.md b/content/en/blog/say-hello-to-akrmq/index.md new file mode 100644 index 0000000..b3e613b --- /dev/null +++ b/content/en/blog/say-hello-to-akrmq/index.md @@ -0,0 +1,10 @@ +--- +title: "Say hello to ArkMQ πŸ‘‹" +description: "Introducing ArkMQ, collection of container images to allow users to deploy the ActiveMQ Artemis Broker from a simple standalone docker image to a fully blown Operator controlled deployment." +lead: "Introducing ArkMQ, collection of container images to allow users to deploy the ActiveMQ Artemis Broker from a simple standalone docker image to a fully blown Operator controlled deployment." +date: 2020-04-18T10:07:21+06:00 +lastmod: 2020-04-18T10:07:21+06:00 +draft: false +weight: 50 +contributors: ["Domenico Francesco Bruscino"] +--- diff --git a/content/en/blog/say-hello-to-artemiscloud/index.md b/content/en/blog/say-hello-to-artemiscloud/index.md deleted file mode 100644 index feb318a..0000000 --- a/content/en/blog/say-hello-to-artemiscloud/index.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: "Say hello to ArtemisCloud πŸ‘‹" -description: "Introducing ArtemisCloud, collection of container images to allow users to deploy the ActiveMQ Artemis Broker from a simple standalone docker image to a fully blown Operator controlled deployment." -lead: "Introducing ArtemisCloud, collection of container images to allow users to deploy the ActiveMQ Artemis Broker from a simple standalone docker image to a fully blown Operator controlled deployment." -date: 2020-04-18T10:07:21+06:00 -lastmod: 2020-04-18T10:07:21+06:00 -draft: false -weight: 50 -contributors: ["Domenico Francesco Bruscino"] ---- diff --git a/content/en/community/_index.md b/content/en/community/_index.md index ad554b6..dd16aa5 100644 --- a/content/en/community/_index.md +++ b/content/en/community/_index.md @@ -2,10 +2,10 @@ title: "Community" subtitle: "" # meta description -description: "ArtemisCloud.io is a collection of container images that provide a way to deploy the Apache ActiveMQ Artemis Broker on Kubernetes." +description: "ArkMQ is a collection of container images that provide a way to deploy the Apache ActiveMQ Artemis Broker on Kubernetes." draft: false --- -ArtemisCloud is a community driven project that can only flourish with contributions from people like yourselves. Jump in +ArkMQ is a community driven project that can only flourish with contributions from people like yourselves. Jump in and become part of a growing open source cloud driven project. diff --git a/content/en/community/bug.md b/content/en/community/bug.md index e98dabc..0aa9130 100644 --- a/content/en/community/bug.md +++ b/content/en/community/bug.md @@ -7,5 +7,5 @@ image: "images/bugs.png" type: "social" --- -If you come across any bugs or have ideas for improvments then you can raise a github issue on the project, for instance [https://github.com/artemiscloud/activemq-artemis-operator/issues](https://github.com/artemiscloud/activemq-artemis-operator/issues) +If you come across any bugs or have ideas for improvments then you can raise a github issue on the project, for instance [https://github.com/arkmq-org/activemq-artemis-operator/issues](https://github.com/arkmq-org/activemq-artemis-operator/issues) diff --git a/content/en/community/contacts.md b/content/en/community/contacts.md index 0b5c0f6..10c488a 100644 --- a/content/en/community/contacts.md +++ b/content/en/community/contacts.md @@ -7,4 +7,4 @@ image: "images/code.png" draft: false --- -The best way to contact folks in the community is by using [github discussions](https://github.com/artemiscloud/activemq-artemis-operator/discussions) \ No newline at end of file +The best way to contact folks in the community is by using [github discussions](https://github.com/arkmq-org/activemq-artemis-operator/discussions) \ No newline at end of file diff --git a/content/en/community/github.md b/content/en/community/github.md index 4999283..e7dd534 100644 --- a/content/en/community/github.md +++ b/content/en/community/github.md @@ -7,5 +7,5 @@ image: "images/code.png" draft: false --- -Without the community contributing code we have nothing, take a look at our [github organisation](https://github.com/artemiscloud) +Without the community contributing code we have nothing, take a look at our [github organisation](https://github.com/arkmq-org) and see if there is a project to contribute to. \ No newline at end of file diff --git a/content/en/community/twitter.md b/content/en/community/twitter.md index 820fb26..c030124 100644 --- a/content/en/community/twitter.md +++ b/content/en/community/twitter.md @@ -7,4 +7,4 @@ image: "images/twitter.png" draft: false --- -To keep up to date with all the ArtemisCloud release and any other important news follow us at [https://twitter.com/artemiscloudio](https://twitter.com/artemiscloudio) \ No newline at end of file +To keep up to date with all the ArkMQ release and any other important news follow us at [https://twitter.com/arkmq_org](https://twitter.com/arkmq_org) \ No newline at end of file diff --git a/content/en/community/website.md b/content/en/community/website.md index 73e2026..698cc35 100644 --- a/content/en/community/website.md +++ b/content/en/community/website.md @@ -7,5 +7,5 @@ image: "images/website.png" draft: false --- -You can contribute to this website by forking [artemiscloud.github.io](https://github.com/artemiscloud/artemiscloud.github.io) and raising a PR. +You can contribute to this website by forking [arkmq-org.github.io](https://github.com/arkmq-org/arkamq-org.github.io) and raising a PR. Feel free to add a blog post, provide content or documentation. \ No newline at end of file diff --git a/content/en/contact/index.md b/content/en/contact/index.md index 3f012fd..329e808 100644 --- a/content/en/contact/index.md +++ b/content/en/contact/index.md @@ -7,4 +7,4 @@ draft: true images: [] --- -{{< email user="info" domain="artemiscloud.io" >}} +{{< email user="info" domain="arkmq.org" >}} diff --git a/content/en/contributors/_index.md b/content/en/contributors/_index.md index aeed206..04ebb5b 100644 --- a/content/en/contributors/_index.md +++ b/content/en/contributors/_index.md @@ -1,10 +1,10 @@ --- title: "Contributors" -description: "The ArtemisCloud contributors." +description: "The ArkMQ contributors." date: 2020-10-06T08:50:29+00:00 lastmod: 2020-10-06T08:50:29+00:00 draft: false images: [] --- -The ArtemisCloud contributors. +The ArkMQ contributors. diff --git a/content/en/docs/_index.md b/content/en/docs/_index.md index d9eac7e..15e4cc5 100644 --- a/content/en/docs/_index.md +++ b/content/en/docs/_index.md @@ -1,6 +1,6 @@ --- title : "Docs" -description: "Docs ArtemisCloud." +description: "Docs ArkMQ." lead: "" date: 2020-10-06T08:48:23+00:00 lastmod: 2020-10-06T08:48:23+00:00 diff --git a/content/en/docs/getting-started/introduction.md b/content/en/docs/getting-started/introduction.md index dfe5c26..82305ce 100644 --- a/content/en/docs/getting-started/introduction.md +++ b/content/en/docs/getting-started/introduction.md @@ -1,7 +1,7 @@ --- title: Introduction -description: ArtemisCloud.io is a collection of container images that provide a way to deploy the Apache ActiveMQ Artemis Broker on Kubernetes. -lead: ArtemisCloud.io is a collection of container images that provide a way to deploy the Apache ActiveMQ Artemis Broker on Kubernetes. +description: ArkMQ is a collection of container images that provide a way to deploy the Apache ActiveMQ Artemis Broker on Kubernetes. +lead: ArkMQ is a collection of container images that provide a way to deploy the Apache ActiveMQ Artemis Broker on Kubernetes. date: 2020-10-06T08:48:57.000Z lastmod: 2020-10-06T08:48:57.000Z draft: false @@ -13,19 +13,19 @@ toc: true ## Welcome -Welcome to The ArtemisCloud documentation. This documentation is open source and can be found at [here](https://github.com/artemiscloud/activemq-artemis-operator/tree/main/docs). All contributions are welcome. +Welcome to The ArkMQ documentation. This documentation is open source and can be found at [here](https://github.com/arkmq-org/activemq-artemis-operator/tree/main/docs). All contributions are welcome. ## Quick Start -One page summary of how to start a new ArtemisCloud project. [Quick Start β†’]({{< relref "quick-start" >}}) +One page summary of how to start a new ArkMQ project. [Quick Start β†’]({{< relref "quick-start" >}}) ## How to contribute to the docs -You can contribute to these docs by sending a Pull Request to the [activemq-artemis-operator](https://github.com/artemiscloud/activemq-artemis-operator) Github repository. -Each chapter is a single markdown file found under the [docs](https://github.com/artemiscloud/activemq-artemis-operator/tree/main/docs) directory. -Simply update an existing chapter or add a new file for a new one. If you add a new on you should update the [\_index.md](https://github.com/artemiscloud/activemq-artemis-operator/blob/main/docs/_index.md) +You can contribute to these docs by sending a Pull Request to the [activemq-artemis-operator](https://github.com/arkmq-org/activemq-artemis-operator) Github repository. +Each chapter is a single markdown file found under the [docs](https://github.com/arkmq-org/activemq-artemis-operator/tree/main/docs) directory. +Simply update an existing chapter or add a new file for a new one. If you add a new on you should update the [\_index.md](https://github.com/arkmq-org/activemq-artemis-operator/blob/main/docs/_index.md) file with the new chapter . ## Help -Get help on ArtemisCloud.io. [Help β†’]({{< relref "operator" >}}) +Get help on ArkMQ. [Help β†’]({{< relref "operator" >}}) diff --git a/content/en/docs/getting-started/quick-start.md b/content/en/docs/getting-started/quick-start.md index 52110a7..c67e669 100644 --- a/content/en/docs/getting-started/quick-start.md +++ b/content/en/docs/getting-started/quick-start.md @@ -1,7 +1,7 @@ --- title: "Quick Start" -description: "One page summary of how to start a new ArtemisCloud project." -lead: "One page summary of how to start a new ArtemisCloud project." +description: "One page summary of how to start a new ArkMQ project." +lead: "One page summary of how to start a new ArkMQ project." date: 2020-11-16T13:59:39+01:00 lastmod: 2020-11-16T13:59:39+01:00 draft: false @@ -30,7 +30,7 @@ You can install a [Minikube](https://minikube.sigs.k8s.io/docs/) or a [CodeReady ## Getting the code and build the image -To launch the operator you will need to clone the [activemq-artemis-operator](https://github.com/artemiscloud/activemq-artemis-operator) and checkout the main branch. +To launch the operator you will need to clone the [activemq-artemis-operator](https://github.com/arkmq-org/activemq-artemis-operator) and checkout the main branch. (Optional) Follow the [building]({{< ref "../help/building.md" >}}) instructions, tag, and push it into your project namespace. @@ -346,7 +346,7 @@ configuration information as files to be used in the artemis configuration. One redefine the log4j file used by artemis to log information. [Here](https://activemq.apache.org/components/artemis/documentation/latest/logging.html#logging) you can find details about artemis logging configuration. To use a custom logging you will need a log4j configuration file. The default log4j configuration file can be used as -an initial example and can be downloaded from [here](https://raw.githubusercontent.com/artemiscloud/activemq-artemis-broker-kubernetes-image/main/modules/activemq-artemis-launch/added/log4j2.properties) +an initial example and can be downloaded from [here](https://raw.githubusercontent.com/arkmq-org/activemq-artemis-broker-kubernetes-image/main/modules/activemq-artemis-launch/added/log4j2.properties) Assuming you already have the operator deployed, in our example we are going to modify the default logging file and enable the audit logging. You will need to modify the log4j2.properties file and change the lines as below: diff --git a/content/en/docs/help/_index.md b/content/en/docs/help/_index.md index 9d7fef5..3ebf889 100644 --- a/content/en/docs/help/_index.md +++ b/content/en/docs/help/_index.md @@ -1,6 +1,6 @@ --- title: "Help" -description: "Help ArtemisCloud." +description: "Help ArkMQ." lead: "" date: 2020-10-06T08:49:15+00:00 lastmod: 2020-10-06T08:49:15+00:00 diff --git a/content/en/docs/help/building.md b/content/en/docs/help/building.md index 9b0b502..42151cb 100644 --- a/content/en/docs/help/building.md +++ b/content/en/docs/help/building.md @@ -1,7 +1,7 @@ --- title: "Building" -description: "Building ArtemisCloud.io" -lead: "Building ArtemisCloud.io" +description: "Building ArkMQ" +lead: "Building ArkMQ" date: 2020-10-06T08:49:31+00:00 lastmod: 2020-10-06T08:49:31+00:00 draft: false @@ -37,7 +37,7 @@ Install [operator-sdk](https://sdk.operatorframework.io/) following [this guide] ## Get the code ```$xslt -git clone https://github.com/artemiscloud/activemq-artemis-operator +git clone https://github.com/arkmq-org/activemq-artemis-operator cd activemq-artemis-operator git checkout main ``` diff --git a/content/en/docs/help/bundle.md b/content/en/docs/help/bundle.md index 33b0427..d62597b 100644 --- a/content/en/docs/help/bundle.md +++ b/content/en/docs/help/bundle.md @@ -1,7 +1,7 @@ --- title: "Bundle" -description: "Bundle ArtemisCloud.io" -lead: "Bundle ArtemisCloud.io" +description: "Bundle ArkMQ" +lead: "Bundle ArkMQ" date: 2020-10-06T08:49:31+00:00 lastmod: 2020-10-06T08:49:31+00:00 draft: false @@ -18,7 +18,7 @@ toc: true ## About the Operator Lifecycle Manager (OLM) The [Operator Lifecycle Manager](https://olm.operatorframework.io/) can help users to install and manage operators. -The ArtemisCloud operator can be built into a bundle image and installed into OLM. +The ArkMQ operator can be built into a bundle image and installed into OLM. ## Building @@ -89,8 +89,8 @@ metadata: spec: sourceType: grpc image: quay.io/hgao/operator-catalog:v0.0.1 - displayName: ArtemisCloud Index - publisher: ArtemisCloud + displayName: ArkMQ Index + publisher: ArkMQ updateStrategy: registryPoll: interval: 10m diff --git a/content/en/docs/help/custom-resources.md b/content/en/docs/help/custom-resources.md index 734c6f8..3a3dad8 100644 --- a/content/en/docs/help/custom-resources.md +++ b/content/en/docs/help/custom-resources.md @@ -1,7 +1,7 @@ --- title: "Custom Resources" -description: "Custom Resource ArtemisCloud.io" -lead: "Custom Resource ArtemisCloud.io" +description: "Custom Resource ArkMQ" +lead: "Custom Resource ArkMQ" date: 2020-10-06T08:49:31+00:00 lastmod: 2020-10-06T08:49:31+00:00 draft: false @@ -21,7 +21,7 @@ The following sub-sections detail the configuration items that you can set in Cu broker and addressing CRDs. ### Broker Custom Resource configuration reference -A CR instance based on the main broker CRD enables you to configure brokers for deployment in a Kubernetes project, see the [artemiscloud/activemq-artemis-operator CRDs](https://doc.crds.dev/github.com/artemiscloud/activemq-artemis-operator). The following is the full CRD yaml file +A CR instance based on the main broker CRD enables you to configure brokers for deployment in a Kubernetes project, see the [arkmq-org/activemq-artemis-operator CRDs](https://doc.crds.dev/github.com/arkmq-org/activemq-artemis-operator). The following is the full CRD yaml file ```yaml apiVersion: apiextensions.k8s.io/v1 diff --git a/content/en/docs/help/images.md b/content/en/docs/help/images.md index e3e2236..7c3ad07 100644 --- a/content/en/docs/help/images.md +++ b/content/en/docs/help/images.md @@ -1,7 +1,7 @@ --- title: "Images" -description: "Images ArtemisCloud.io" -lead: "Images ArtemisCloud.io" +description: "Images ArkMQ" +lead: "Images ArkMQ" date: 2020-10-06T08:49:31+00:00 lastmod: 2020-10-06T08:49:31+00:00 draft: false @@ -13,14 +13,14 @@ weight: 630 toc: true --- -## Overview of the ArtemisCloud Container images +## Overview of the ArkMQ Container images Docs to Follow ### The basic Container Image The Basic Broker Container Image is the simplest of images to get started with, it uses environment variables to configure the broker and then starts it. -You can find the basic Broker Container Image at [quay.io](https://quay.io/repository/artemiscloud/activemq-artemis-broker) +You can find the basic Broker Container Image at [quay.io](https://quay.io/repository/arkmq-org/activemq-artemis-broker) ### The Kubernetes Image diff --git a/content/en/docs/help/operator.md b/content/en/docs/help/operator.md index 23a56e3..e217968 100644 --- a/content/en/docs/help/operator.md +++ b/content/en/docs/help/operator.md @@ -1,7 +1,7 @@ --- title: "Operator" -description: "Operator ArtemisCloud.io" -lead: "Operator ArtemisCloud.io" +description: "Operator ArkMQ" +lead: "Operator ArkMQ" date: 2020-10-06T08:49:31+00:00 lastmod: 2020-10-06T08:49:31+00:00 draft: false @@ -13,7 +13,7 @@ weight: 630 toc: true --- -## Overview of the ArtemisCloud Operator Custom Resource Definitions +## Overview of the ArkMQ Operator Custom Resource Definitions In general, a Custom Resource Definition (CRD) is a schema of configuration items that you can modify for a custom Kubernetes object deployed with an Operator. By creating a corresponding Custom Resource (CR) instance, you can specify values for @@ -74,7 +74,7 @@ For more information about provisioning persistent storage in Kubernetes, see [U ## Installing the Operator using the CLI This section shows how to use the Kubernetes command-line interface (CLI) to deploy the latest version of -the Operator for ArtemisCloud in your Kubernetes project. +the Operator for ArkMQ in your Kubernetes project. If you intend to deploy brokers with persistent storage and do not have container-native storage in your Kubernetes cluster, you need to manually provision Persistent Volumes (PVs) and ensure that they are available to be claimed by the Operator. @@ -134,9 +134,9 @@ After editing the Subscription yaml as such, save it and the operator will resta ### Getting the Operator code -This procedure shows how to access and prepare the code you need to install the latest version of the Operator for ArtemisCloud . +This procedure shows how to access and prepare the code you need to install the latest version of the Operator for ArkMQ . -Download the latest version of the Operator from https://github.com/artemiscloud/activemq-artemis-operator/tags +Download the latest version of the Operator from https://github.com/arkmq-org/activemq-artemis-operator/tags When the download has completed, move the archive to your chosen installation directory. ```shell script @@ -261,7 +261,7 @@ spec: template: spec: containers: - image: quay.io/artemiscloud/activemq-artemis-operator:latest + image: quay.io/arkmq-org/activemq-artemis-operator:latest ``` Deploy the Operator. @@ -305,7 +305,7 @@ The following procedure shows how to use a Custom Resource (CR) instance to crea Prerequisites -1. You must have already installed the ArtemisCloud Operator. +1. You must have already installed the ArkMQ Operator. 2. To use the Kubernetes command-line interface (CLI) to install the ActiveMQ Artemis Operator, see [Installing the Operator](#installing-the-operator-using-the-cli). @@ -337,7 +337,7 @@ spec: ``` Observe that the sample CR uses a naming convention of **ex-aao**. This naming convention denotes that the CR is an example -resource for the ArtemisCloud (based on the ActiveMQ Artemis project) Operator. When you deploy this sample CR, the resulting +resource for the ArkMQ (based on the ActiveMQ Artemis project) Operator. When you deploy this sample CR, the resulting Stateful Set uses the name **ex-aao-ss**. Furthermore, broker Pods in the deployment are directly based on the Stateful Set name, for example, **ex-aao-ss-0**, **ex-aao-ss-1**, and so on. @@ -477,7 +477,7 @@ via the **kubectl scale** command. For example, suppose you use **kubectl** scal but the value of **deploymentPlan.size** in your CR is still 3. In this case, Kubernetes initially scales the deployment down to two brokers. However, when the scaledown operation is complete, the Operator restores the deployment to three brokers, as specified in the CR. -3. As described in [Deploying the Operator using the CLI](#deploying-the-operator-using-the-cli), if you create a broker deployment with persistent storage (that is, by setting persistenceEnabled=true in your CR), you might need to provision Persistent Volumes (PVs) for the ArtemisCloud Operator to claim for your broker Pods. If you scale down the size of your broker deployment, the Operator releases any PVs that it previously claimed for the broker Pods that are now shut down. However, if you remove your broker deployment by deleting your CR, ArtemisCloud Operator does not release Persistent Volume Claims (PVCs) for any broker Pods that are still in the deployment when you remove it. In addition, these unreleased PVs are unavailable to any new deployment. In this case, you need to manually release the volumes. For more information, see Releasing volumes in the Kubernetes documentation. +3. As described in [Deploying the Operator using the CLI](#deploying-the-operator-using-the-cli), if you create a broker deployment with persistent storage (that is, by setting persistenceEnabled=true in your CR), you might need to provision Persistent Volumes (PVs) for the ArkMQ Operator to claim for your broker Pods. If you scale down the size of your broker deployment, the Operator releases any PVs that it previously claimed for the broker Pods that are now shut down. However, if you remove your broker deployment by deleting your CR, ArkMQ Operator does not release Persistent Volume Claims (PVCs) for any broker Pods that are still in the deployment when you remove it. In addition, these unreleased PVs are unavailable to any new deployment. In this case, you need to manually release the volumes. For more information, see Releasing volumes in the Kubernetes documentation. 4. During an active scaling event, any further changes that you apply are queued by the Operator and executed only when scaling is complete. For example, suppose that you scale the size of your deployment down from four brokers to one. Then, while scaledown is taking place, you also change the values of the broker administrator user name and password. In this case, the Operator queues the user name and password changes until the deployment is running with one active broker. @@ -600,7 +600,7 @@ spec: #### The Readiness Probe As with the Liveness Probe the Readiness probe has a default probe if not configured. Unlike the readiness probe this is -a script that is shipped in the Kubernetes Image, this can be found [here](https://github.com/artemiscloud/activemq-artemis-broker-kubernetes-image/blob/main/modules/activemq-artemis-launch/added/readinessProbe.sh) +a script that is shipped in the Kubernetes Image, this can be found [here](https://github.com/arkmq-org/activemq-artemis-broker-kubernetes-image/blob/main/modules/activemq-artemis-launch/added/readinessProbe.sh) The script will try to establish a tcp connection to each port configured in the broker.xml. @@ -741,7 +741,7 @@ spec: It is possible to configure ResourceTemplate(s) for resources that are managed by the operator. The TemplateType contains Labels and Annotations with an optional Selector. If the selector is empty the template matches all resources. Othewise it can be used to restrict what is matched. -Note: the relevant variables supported by [`ingressHost`](https://github.com/artemiscloud/activemq-artemis-operator/issues/614) in the CRD can be referenced in keys and values for both labels and annotations. +Note: the relevant variables supported by [`ingressHost`](https://github.com/arkmq-org/activemq-artemis-operator/issues/614) in the CRD can be referenced in keys and values for both labels and annotations. In the following example, the annotation "someKey=someValue" is added to all Services ```yaml @@ -805,7 +805,7 @@ spec: ## Configuring Logging for Brokers By default the operator deploys a broker with a default logging configuration that comes with the [Artemis container image] -(https://github.com/artemiscloud/activemq-artemis-broker-kubernetes-image). Broker logs its messages to console only. +(https://github.com/arkmq-org/activemq-artemis-broker-kubernetes-image). Broker logs its messages to console only. Users can change the broker logging configuration by providing their own in a configmap or secret. The name of the configmap or secret must have the suffix **-logging-config**. There must a key **logging.properties** and the value must of the full content of the logging configuration. (The broker is using slf4j with @@ -951,7 +951,7 @@ spec: endpoints: - port: wconsj ``` -For a complete example please refer to this [artemiscloud example](https://github.com/artemiscloud/artemiscloud-examples/tree/main/operator/prometheus). +For a complete example please refer to this [arkmq example](https://github.com/arkmq-org/arkmq-examples/tree/main/operator/prometheus). ## Configuring PodDisruptionBudget for broker deployment diff --git a/content/en/docs/tutorials/cert-manager-and-trust-manager.md b/content/en/docs/tutorials/cert-manager-and-trust-manager.md index 51ed6f8..d19d6a9 100644 --- a/content/en/docs/tutorials/cert-manager-and-trust-manager.md +++ b/content/en/docs/tutorials/cert-manager-and-trust-manager.md @@ -199,7 +199,7 @@ kubectl create secret generic ssl-acceptor-ssl-secret -n myproject \ --from-literal=trustStorePassword=changeit ``` -## Deploy ArtemisCloud operator +## Deploy ArkMQ operator Operator will create ActiveMQ resources based on custom resources definitions (CRD). @@ -218,7 +218,7 @@ activemq-artemis-operator-58bb658f4c-zcqmw 1/1 Running 0 7m32s ## Deploy a broker -Example of the broker CRD is located in the local repository cloned during activities from section **Deploy ArtemisCloud operator**. +Example of the broker CRD is located in the local repository cloned during activities from section **Deploy ArkMQ operator**. Replace **myproject** with actual namespace your brokers are installed in. @@ -230,7 +230,7 @@ kubectl apply -f examples/artemis/artemis_ssl_acceptor_cert_and_trust_managers.y ## Deploy a queue -Example of the queue CRD is located in the local repository cloned during activities from section **Deploy ArtemisCloud operator**. +Example of the queue CRD is located in the local repository cloned during activities from section **Deploy ArkMQ operator**. Deploy a queue with (beeing on the root folder of this repository): diff --git a/content/en/docs/tutorials/deploybasicimage.md b/content/en/docs/tutorials/deploybasicimage.md index ac66c4c..6783fdd 100644 --- a/content/en/docs/tutorials/deploybasicimage.md +++ b/content/en/docs/tutorials/deploybasicimage.md @@ -15,7 +15,7 @@ toc: true The basic Broker Container image is the easiest way to get the broker up and running as a container, we'll explain what it is and how to run it locally. The Basic Broker Container Image is the simplest of images to get started with, it uses environment variables to configure the broker and then starts it. -You can find the basic Broker Container Image at [quay.io](https://quay.io/repository/artemiscloud/activemq-artemis-broker) +You can find the basic Broker Container Image at [quay.io](https://quay.io/repository/arkmq-org/activemq-artemis-broker) You can use your favourite tool to run the container but for this example we are using docker. @@ -23,19 +23,19 @@ All you need to do is execute the docker run command which will download the bas in this instance we are using the latest dev tag but you could choose a released version if needed. ```shell script - docker run -e AMQ_USER=admin -e AMQ_PASSWORD=admin --name artemis quay.io/artemiscloud/activemq-artemis-broker:dev.latest + docker run -e AMQ_USER=admin -e AMQ_PASSWORD=admin --name artemis quay.io/arkmq-org/activemq-artemis-broker:dev.latest ``` This now should download the latest image and run it, you should see: ```shell script -dev.latest: Pulling from artemiscloud/activemq-artemis-broker +dev.latest: Pulling from arkmq-org/activemq-artemis-broker eae19a56e9c6: Pull complete be73321c7956: Pull complete 4b32e1d9d455: Pull complete Digest: sha256:891dc91d789d93ed474df00355bd173c3980158aa68cba0737a81b920fc0bf2f -Status: Downloaded newer image for quay.io/artemiscloud/activemq-artemis-broker:dev.latest +Status: Downloaded newer image for quay.io/arkmq-org/activemq-artemis-broker:dev.latest Creating Broker with args --user XXXXX --password XXXXX --role admin --name broker --allow-anonymous --http-host 172.17.0.2 --host 172.17.0.2 --force Creating ActiveMQ Artemis instance at: /home/jboss/broker @@ -64,7 +64,7 @@ Running Broker 2021-01-29 10:05:09,372 INFO [org.apache.activemq.artemis] AMQ241004: Artemis Console available at http://172.17.0.2:8161/console ``` -Well done you have now deployed your first artemiscloud image. Now we want to expose the broker to the outside world so +Well done you have now deployed your first arkmq image. Now we want to expose the broker to the outside world so stop the broker and remove the image. ```shell script @@ -74,7 +74,7 @@ docker rm artemis Now re run the broker pod and expose the broker by publishing the broker's console port 8161 on the docker hosts machine port 80. ```shell script -docker run -e AMQ_USER=admin -e AMQ_PASSWORD=admin -p80:8161 --name artemis quay.io/artemiscloud/activemq-artemis-broker:dev.latest +docker run -e AMQ_USER=admin -e AMQ_PASSWORD=admin -p80:8161 --name artemis quay.io/arkmq-org/activemq-artemis-broker:dev.latest ``` Now open up a browser and go to http://localhost/console and login using the username and password you provided in the docker command. @@ -87,4 +87,4 @@ artemis producer ``` For more information on ActiveMQ Artemis please read the [Artemis Documentation](https://activemq.apache.org/components/artemis/documentation/) -and for available environment properties to set you can check the [image.yaml](https://github.com/artemiscloud/activemq-artemis-broker-image/blob/master/image.yaml) +and for available environment properties to set you can check the [image.yaml](https://github.com/arkmq-org/activemq-artemis-broker-image/blob/master/image.yaml) diff --git a/content/en/docs/tutorials/external_mqtt_clients.md b/content/en/docs/tutorials/external_mqtt_clients.md index ab05904..1b1ecbc 100644 --- a/content/en/docs/tutorials/external_mqtt_clients.md +++ b/content/en/docs/tutorials/external_mqtt_clients.md @@ -13,7 +13,7 @@ toc: true When you expose an acceptor to external clients (that is, by setting the value of the expose parameter to true), the Operator automatically creates an ingress on Kubernetes or a route on OpenShift for each broker pod of the deployment. An external client can connect to the broker by specifying the full host name of the ingress/route created for the broker pod. # Prerequisite -Before you start you need to have access to a running Kubernetes cluster environment. A [Minikube](https://minikube.sigs.k8s.io/docs/start/) with [Ingress](https://kubernetes.io/docs/tasks/access-application-cluster/ingress-minikube/) running on your laptop will just do fine. The ArtemisCloud operator also runs in Openshift cluster environment like [CodeReady Container](https://developers.redhat.com/products/codeready-containers/overview). In this blog we assume you have Kubernetes cluster environment. Execute the following command to enable Ingress in minikube: +Before you start you need to have access to a running Kubernetes cluster environment. A [Minikube](https://minikube.sigs.k8s.io/docs/start/) with [Ingress](https://kubernetes.io/docs/tasks/access-application-cluster/ingress-minikube/) running on your laptop will just do fine. The ArkMQ operator also runs in Openshift cluster environment like [CodeReady Container](https://developers.redhat.com/products/codeready-containers/overview). In this blog we assume you have Kubernetes cluster environment. Execute the following command to enable Ingress in minikube: ```shell script $ minikube addons enable ingress @@ -26,8 +26,8 @@ $ minikube addons enable ingress $ minikube kubectl -- patch deployment -n ingress-nginx ingress-nginx-controller --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value":"--enable-ssl-passthrough"}]' ``` -# Deploy ArtemisCloud operator -First you need to deploy the ArtemisCloud operator. +# Deploy ArkMQ operator +First you need to deploy the ArkMQ operator. If you are not sure how to deploy the operator take a look at [this blog]({{< relref "using_operator.md" >}}). # Download the test certficates from Apache ActiveMQ Artemis @@ -75,10 +75,10 @@ EOF Use the following command to publish a message with mosquitto_pub from your host: ```shell script -$ mosquitto_pub -d --insecure -t "test" -m "test" -u admin -P admin -h artemis-mqtt-ssl-my-acceptor-0-svc-ing.apps.artemiscloud.io -p 443 --cafile server-ca.crt +$ mosquitto_pub -d --insecure -t "test" -m "test" -u admin -P admin -h artemis-mqtt-ssl-my-acceptor-0-svc-ing.apps.arkmq.org -p 443 --cafile server-ca.crt ``` Alternatively you can execute mosquitto_pub from the eclipse-mosquitto container running on your host with [podman](https://podman.io/). Use the following command to publish a message with mosquitto_pub from the eclipse-mosquitto container running on your host: ```shell script -$ podman run --name mosquitto_pub -it --rm --add-host artemis-mqtt-ssl-my-acceptor-0-svc-ing.apps.artemiscloud.io:$(minikube ip) --network host --entrypoint /usr/bin/mosquitto_pub -v ${PWD}/server-ca.crt:/mosquitto/config/server-ca.crt:Z eclipse-mosquitto -d --insecure -t "test" -m "test" -u admin -P admin -h artemis-mqtt-ssl-my-acceptor-0-svc-ing.apps.artemiscloud.io -p 443 --cafile /mosquitto/config/server-ca.crt +$ podman run --name mosquitto_pub -it --rm --add-host artemis-mqtt-ssl-my-acceptor-0-svc-ing.apps.arkmq.org:$(minikube ip) --network host --entrypoint /usr/bin/mosquitto_pub -v ${PWD}/server-ca.crt:/mosquitto/config/server-ca.crt:Z eclipse-mosquitto -d --insecure -t "test" -m "test" -u admin -P admin -h artemis-mqtt-ssl-my-acceptor-0-svc-ing.apps.arkmq.org -p 443 --cafile /mosquitto/config/server-ca.crt ``` diff --git a/content/en/docs/tutorials/initcontainer.md b/content/en/docs/tutorials/initcontainer.md index de17ac9..4319d7b 100644 --- a/content/en/docs/tutorials/initcontainer.md +++ b/content/en/docs/tutorials/initcontainer.md @@ -10,20 +10,20 @@ weight: 110 toc: true --- -Starting from [v0.18.1](https://github.com/artemiscloud/activemq-artemis-operator/tree/v0.18.1), the ArtemisCloud Operator +Starting from [v0.18.1](https://github.com/arkmq-org/activemq-artemis-operator/tree/v0.18.1), the ArkMQ Operator enables you to specify a **custom Init Container image**. Specifying a custom Init Container image allows you to provide your own broker configuration within the Operator framework. ### What is a custom Init Container image? -The ArtemisCloud Operator uses a [Custom Resource Definition (CRD)](https://github.com/artemiscloud/activemq-artemis-operator/blob/v0.18.1/deploy/crds/broker_activemqartemis_crd.yaml) to define the broker configuration. In Kubernetes, a CRD is a schema of configuration items or parameters. By creating a corresponding Custom Resource (CR) instance, you can specify values for configuration items in the CRD. For example, you can define address settings -in this [sample CR file](https://github.com/artemiscloud/activemq-artemis-operator/blob/v0.18.1/deploy/examples/artemis-basic-address-settings-deployment.yaml). +The ArkMQ Operator uses a [Custom Resource Definition (CRD)](https://github.com/arkmq-org/activemq-artemis-operator/blob/v0.18.1/deploy/crds/broker_activemqartemis_crd.yaml) to define the broker configuration. In Kubernetes, a CRD is a schema of configuration items or parameters. By creating a corresponding Custom Resource (CR) instance, you can specify values for configuration items in the CRD. For example, you can define address settings +in this [sample CR file](https://github.com/arkmq-org/activemq-artemis-operator/blob/v0.18.1/deploy/examples/artemis-basic-address-settings-deployment.yaml). For configuration that _isn't_ exposed in the CRD, you can specify a custom Init Container image to manipulate or add to the configuration that has been created by the Operator. When the CR is deployed and the broker instance is created, the Operator will then run a user-provided post-configuration script. ### How it works -Internally, the ArtemisCloud Operator uses a specialized container called an _Init Container_ to configure each broker instance. If no custom image for the Init Container has been specified, the Operator uses a [built-in Init Container image](https://quay.io/repository/artemiscloud/activemq-artemis-broker-init), which -is responsible for the configuration. The broker configuration generated by the Init Container is passed to the [broker container image](https://quay.io/repository/artemiscloud/activemq-artemis-broker-kubernetes) to use when launching the broker. +Internally, the ArkMQ Operator uses a specialized container called an _Init Container_ to configure each broker instance. If no custom image for the Init Container has been specified, the Operator uses a [built-in Init Container image](https://quay.io/repository/arkmq-org/activemq-artemis-broker-init), which +is responsible for the configuration. The broker configuration generated by the Init Container is passed to the [broker container image](https://quay.io/repository/arkmq-org/activemq-artemis-broker-kubernetes) to use when launching the broker. -If a custom Init Container image _is_ provided and specified in the Custom Resource (CR), then this is used to create the configuration. Since the custom image is built on top of the ArtemisCloud built-in Init Container image, the custom image first generates the broker configuration that is defined in the CR. Then, the Operator executes the post-configuration (`post-config.sh`) script provided by the custom Init Container. +If a custom Init Container image _is_ provided and specified in the Custom Resource (CR), then this is used to create the configuration. Since the custom image is built on top of the ArkMQ built-in Init Container image, the custom image first generates the broker configuration that is defined in the CR. Then, the Operator executes the post-configuration (`post-config.sh`) script provided by the custom Init Container. For ease of use, the environment variable `CONFIG_INSTANCE_DIR` is set. This environment variable points to the broker instance directory, which has the following structure: @@ -51,10 +51,10 @@ After the `post-config.sh` script is executed, the broker instance is launched w The custom image should follow these predefined rules: - - The custom image must use the ArtemisCloud Operator's [built-in Init Container image](https://quay.io/repository/artemiscloud/activemq-artemis-broker-init) as the base image in its Docker file. For example: + - The custom image must use the ArkMQ Operator's [built-in Init Container image](https://quay.io/repository/arkmq-org/activemq-artemis-broker-init) as the base image in its Docker file. For example: ``` - FROM quay.io/artemiscloud/activemq-artemis-broker-init:0.2.3 + FROM quay.io/arkmq-org/activemq-artemis-broker-init:0.2.3 ... ``` @@ -76,14 +76,14 @@ After the `post-config.sh` script is executed, the broker instance is launched w spec: deploymentPlan: size: 1 - image: quay.io/artemiscloud/activemq-artemis-broker-kubernetes:0.2.1 + image: quay.io/arkmq-org/activemq-artemis-broker-kubernetes:0.2.1 initImage: ... ``` -4. Finally, deploy the CR file in the usual manner. For more information, see [Getting Started with the ArtemisCloud Operator]({{< ref "using_operator" >}} "About Us"). +4. Finally, deploy the CR file in the usual manner. For more information, see [Getting Started with the ArkMQ Operator]({{< ref "using_operator" >}} "About Us"). ### Further information -* A fully working example is available [here](https://github.com/artemiscloud/artemiscloud-examples/tree/main/operator/init/jdbc). +* A fully working example is available [here](https://github.com/arkmq-org/arkmq-examples/tree/main/operator/init/jdbc). -* For issues or suggestions please open an issue at [ArtemisCloud](https://github.com/artemiscloud/activemq-artemis-operator/issues). +* For issues or suggestions please open an issue at [ArkMQ](https://github.com/arkmq-org/activemq-artemis-operator/issues). diff --git a/content/en/docs/tutorials/scaleup_and_scaledown.md b/content/en/docs/tutorials/scaleup_and_scaledown.md index b4cf127..cae2fe1 100644 --- a/content/en/docs/tutorials/scaleup_and_scaledown.md +++ b/content/en/docs/tutorials/scaleup_and_scaledown.md @@ -1,5 +1,5 @@ --- -title: "Scaling Up and Down Brokers with ArtemisCloud Operator" +title: "Scaling Up and Down Brokers with ArkMQ Operator" description: "How to use operator to scale up and down broker pods" draft: false images: [] @@ -10,17 +10,17 @@ weight: 110 toc: true --- -With ArtemisCloud operator one can easily manage the broker clusters. +With ArkMQ operator one can easily manage the broker clusters. Either scaling up number of nodes(pods) when workload is high, or scaling down when some is not needed -- without messages being lost or stuck. ### Prerequisite -Before you start you need have access to a running Kubernetes cluster environment. A [Minikube](https://minikube.sigs.k8s.io/docs/start/) running on your laptop will just do fine. The ArtemisCloud operator also runs in a Openshift cluster environment like [CodeReady Container](https://developers.redhat.com/products/codeready-containers/overview). In this blog we assume you have Kubernetes cluster environment. (If you use CodeReady the client tool is **oc** in place of **kubectl**) +Before you start you need have access to a running Kubernetes cluster environment. A [Minikube](https://minikube.sigs.k8s.io/docs/start/) running on your laptop will just do fine. The ArkMQ operator also runs in a Openshift cluster environment like [CodeReady Container](https://developers.redhat.com/products/codeready-containers/overview). In this blog we assume you have Kubernetes cluster environment. (If you use CodeReady the client tool is **oc** in place of **kubectl**) -### Step 1 - Deploy ArtemisCloud Operator -In this article we are using the [artemiscloud operator repo](https://github.com/artemiscloud/activemq-artemis-operator). In case you haven't done so, clone it to your local disk: +### Step 1 - Deploy ArkMQ Operator +In this article we are using the [arkmq operator repo](https://github.com/arkmq-org/activemq-artemis-operator). In case you haven't done so, clone it to your local disk: ```shell script -$ git clone https://github.com/artemiscloud/activemq-artemis-operator.git +$ git clone https://github.com/arkmq-org/activemq-artemis-operator.git $ cd activemq-artemis-operator ``` @@ -50,7 +50,7 @@ Use your favorite text editor to create a file called **artemis-clustered.yaml** spec: deploymentPlan: size: 1 - image: quay.io/artemiscloud/activemq-artemis-broker-kubernetes:0.2.1 + image: quay.io/arkmq-org/activemq-artemis-broker-kubernetes:0.2.1 persistenceEnabled: true messageMigration: true ``` @@ -62,7 +62,7 @@ $ kubectl create -f artemis-clustered.yaml -n myproject activemqartemis.broker.amq.io/ex-aao created ``` -The custom resource file tells the operator to deploy one broker pod from the image **quay.io/artemiscloud/activemq-artemis-broker-kubernetes:0.2.1**, +The custom resource file tells the operator to deploy one broker pod from the image **quay.io/arkmq-org/activemq-artemis-broker-kubernetes:0.2.1**, configured with **persistenceEnabled: true** and **messageMigration: true**. **persistenceEnabled: true** means the broker persists messages to persistent storage. @@ -90,7 +90,7 @@ To inform the operator that we want to scale from one to two broker pods modify spec: deploymentPlan: size: 2 - image: quay.io/artemiscloud/activemq-artemis-broker-kubernetes:0.2.1 + image: quay.io/arkmq-org/activemq-artemis-broker-kubernetes:0.2.1 persistenceEnabled: true messageMigration: true ``` @@ -186,7 +186,7 @@ Now scale down the cluster from 2 pods to one. Edit the [broker cr](#broker_clus spec: deploymentPlan: size: 1 - image: quay.io/artemiscloud/activemq-artemis-broker-kubernetes:0.2.1 + image: quay.io/arkmq-org/activemq-artemis-broker-kubernetes:0.2.1 persistenceEnabled: true messageMigration: true ``` @@ -221,5 +221,4 @@ It shows queue TEST's message count is **200** now! ### More information -* Check out [artemiscloud project repo](https://github.com/artemiscloud) -* Reach the [dev team at slack](artemiscloudio.slack.com) for questions/issues/help +* Check out [arkmq project repo](https://github.com/arkmq-org) diff --git a/content/en/docs/tutorials/ssl_broker_setup.md b/content/en/docs/tutorials/ssl_broker_setup.md index 0d4038b..28dfa16 100644 --- a/content/en/docs/tutorials/ssl_broker_setup.md +++ b/content/en/docs/tutorials/ssl_broker_setup.md @@ -1,5 +1,5 @@ --- -title: "Setting up SSL connections with ArtemisCloud Operator" +title: "Setting up SSL connections with ArkMQ Operator" description: "An example for setting up ssl connections for broker in kubernetes with operator" draft: false images: [] @@ -10,7 +10,7 @@ weight: 110 toc: true --- -Security is always a concern in a production environment. With ArtemisCloud Operator +Security is always a concern in a production environment. With ArkMQ Operator You can easily configure and set up a broker with ssl-enabled acceptors. The blog explains how to do it. The [ActiveMQ Artemis](https://activemq.apache.org/components/artemis/) broker supports a variety of network protocols(tcp, http, etc) including [SSL(TLS)](https://en.wikipedia.org/wiki/Transport_Layer_Security) secure connections. Underneath it uses [Netty](https://netty.io/) as the base transport layer. @@ -18,10 +18,10 @@ The [ActiveMQ Artemis](https://activemq.apache.org/components/artemis/) broker s This article guides you through the steps to set up a broker to run in kubernetes (Minikube). The broker will listen on a secure port 61617 (ssl over tcp). It also demonstrates sending and receiving messages over secure connections using one-way authentication. ### Prerequisite -Before you start you need have access to a running Kubernetes cluster environment. A [Minikube](https://minikube.sigs.k8s.io/docs/start/) running on your laptop will just do fine. The ArtemisCloud operator also runs in a Openshift cluster environment like [CodeReady Container](https://developers.redhat.com/products/codeready-containers/overview). In this blog we assume you have Kubernetes cluster environment. (If you use CodeReady the client tool is **oc** in place of **kubectl**) +Before you start you need have access to a running Kubernetes cluster environment. A [Minikube](https://minikube.sigs.k8s.io/docs/start/) running on your laptop will just do fine. The ArkMQ operator also runs in a Openshift cluster environment like [CodeReady Container](https://developers.redhat.com/products/codeready-containers/overview). In this blog we assume you have Kubernetes cluster environment. (If you use CodeReady the client tool is **oc** in place of **kubectl**) -### Deploy ArtemisCloud operator -First you need to deploy the ArtemisCloud operator. +### Deploy ArkMQ operator +First you need to deploy the ArkMQ operator. If you are not sure how to deploy the operator take a look at [this blog]({{< relref "using_operator.md" >}}). In this blog post we assume you deployed the operator to a namespace called **myproject**. @@ -122,7 +122,7 @@ metadata: spec: deploymentPlan: size: 1 - image: quay.io/artemiscloud/activemq-artemis-broker-kubernetes:0.2.1 + image: quay.io/arkmq-org/activemq-artemis-broker-kubernetes:0.2.1 acceptors: - name: sslacceptor protocols: all @@ -203,5 +203,5 @@ Now you get an idea how an SSL acceptor is configured and processed by the opera ### More SSL options We have just demonstrated a simplified SSL configuration. In fact the operator supports quite a few more SSL options through the CRD definitions. -You can checkout those options in broker CRD [down here](https://github.com/artemiscloud/activemq-artemis-operator/blob/5183ddc4c2f66e0d270233a3f37340b14e225d80/deploy/crds/broker_activemqartemis_crd.yaml#L45) +You can checkout those options in broker CRD [down here](https://github.com/arkmq-org/activemq-artemis-operator/blob/5183ddc4c2f66e0d270233a3f37340b14e225d80/deploy/crds/broker_activemqartemis_crd.yaml#L45) and also read the [Artemis Doc on configuring transports](https://activemq.apache.org/components/artemis/documentation/latest/configuring-transports.html) for more information. diff --git a/content/en/docs/tutorials/using_operator.md b/content/en/docs/tutorials/using_operator.md index 959b383..b085697 100644 --- a/content/en/docs/tutorials/using_operator.md +++ b/content/en/docs/tutorials/using_operator.md @@ -1,5 +1,5 @@ --- -title: "Using the ArtemisCloud Operator" +title: "Using the ArkMQ Operator" description: "Steps to get operator up and running and basic broker operations" draft: false images: [] @@ -10,21 +10,21 @@ weight: 110 toc: true --- -The [ArtemisCloud](https://github.com/artemiscloud) Operator is a powerful tool that allows you to configure and +The [ArkMQ](https://github.com/arkmq-org) Operator is a powerful tool that allows you to configure and manage ActiveMQ Artemis broker resources in a cloud environment. You can get the Operator running in just a few steps. ### Prerequisite Before you start, you need to have access to a running Kubernetes cluster environment. A [Minikube](https://minikube.sigs.k8s.io/docs/start/) -instance running on your laptop will do fine. The ArtemisCloud Operator can also run in an Openshift cluster environment such as [CodeReady Containers](https://developers.redhat.com/products/codeready-containers/overview). +instance running on your laptop will do fine. The ArkMQ Operator can also run in an Openshift cluster environment such as [CodeReady Containers](https://developers.redhat.com/products/codeready-containers/overview). In this blog post, we assume that you have a Kubernetes cluster environment. **_NOTE:_** If you use CodeReady Containers, the client tool is **oc** rather than **kubectl** ### Step 1 - Preparing for deployment -Clone the ArtemisCloud Operator repo: +Clone the ArkMQ Operator repo: ```shell script - $ git clone https://github.com/artemiscloud/activemq-artemis-operator.git + $ git clone https://github.com/arkmq-org/activemq-artemis-operator.git ``` We will use a namespace called **myproject** to deploy the operator and other resources. If you don't specify a namespace the **default** namespace will be used. @@ -151,7 +151,7 @@ Now, let's create a message queue in the broker: $ kubectl create -f examples/address/address_queue.yaml -n myproject activemqartemisaddress.broker.amq.io/artemis-address-queue created ``` -The _address_queue.yaml_ is another CR supported by the ArtemisCloud Operator. Its content is shown below: +The _address_queue.yaml_ is another CR supported by the ArkMQ Operator. Its content is shown below: ```yaml apiVersion: broker.amq.io/v1beta1 kind: ActiveMQArtemisAddress @@ -207,4 +207,4 @@ Connection brokerURL = tcp://artemis-address-queue-ss-0:61616 ``` ### Further information -* [ArtemisCloud Github Repo](https://github.com/artemiscloud) +* [ArkMQ Github Repo](https://github.com/arkmq-org) diff --git a/content/en/privacy-policy/index.md b/content/en/privacy-policy/index.md index 85c6e67..3c4a6dd 100644 --- a/content/en/privacy-policy/index.md +++ b/content/en/privacy-policy/index.md @@ -20,9 +20,9 @@ __TLDR__: We do not use cookies and we do not collect any personal data. ### Information we collect and what we use it for -We run [Plausible](https://plausible.io/) analytics on artemiscloud.io. The following information is collected: +We run [Plausible](https://plausible.io/) analytics on arkmq.org. The following information is collected: -- __Page URL__. We track the page URL of each page view on this website. We use this to understand which pages have been viewed and how many times a particular page has been viewed. For example: _https://artemiscloud.io/_. +- __Page URL__. We track the page URL of each page view on this website. We use this to understand which pages have been viewed and how many times a particular page has been viewed. For example: _https://arkmq.org/_. - __HTTP Referrer__. We use the referrer string to understand the number of visitors referred to this website from links on other sites. For example: _https://github.com/_. - __Browser__. We use this to understand what browsers people use when visiting this website. This is derived from the User-Agent HTTP header. The full User-Agent is discarded. For example: _Chrome_. - __Operating system__. We use this to understand what operating systems people use when visiting this website. We only use the brand of the operating system and don’t include the version number or any other details. This is derived from the User-Agent HTTP header. The full User-Agent is discarded. For example: _GNU/Linux_. diff --git a/content/en/versions.md b/content/en/versions.md index 8615c0b..1ff7183 100644 --- a/content/en/versions.md +++ b/content/en/versions.md @@ -1,7 +1,7 @@ --- title: "Versions" description: "" -lead: "An appendix of hosted documentation for nearly every release of ArtemisCloud." +lead: "An appendix of hosted documentation for nearly every release of ArkMQ." date: 2021-09-24T08:50:23+02:00 lastmod: 2021-09-24T08:50:23+02:00 draft: true diff --git a/netlify.toml b/netlify.toml index f026dbc..9d0d850 100644 --- a/netlify.toml +++ b/netlify.toml @@ -25,7 +25,7 @@ package = "netlify-plugin-submit-sitemap" [plugins.inputs] - baseUrl = "https://artemiscloud.netlify.app/" + baseUrl = "https://arkmq.netlify.app/" sitemapPath = "/sitemap.xml" ignorePeriod = 0 providers = [ diff --git a/package-lock.json b/package-lock.json index b9a144b..793c211 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,11 +1,11 @@ { - "name": "@artemiscloud/artemiscloud.github.io", + "name": "@arkmq-org/arkmq-org.github.io", "version": "0.4.3", "lockfileVersion": 2, "requires": true, "packages": { "": { - "name": "@artemiscloud/artemiscloud.github.io", + "name": "@arkmq-org/arkmq-org.github.io", "version": "0.4.3", "hasInstallScript": true, "license": "MIT", diff --git a/package.json b/package.json index 4b28cb6..06cf8e1 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { - "name": "@artemiscloud/artemiscloud.github.io", - "description": "ArtemisCloud website", + "name": "@arkmq-org/arkmq-org.github.io", + "description": "ArkMQ website", "version": "0.4.3", "engines": { "node": ">=16.15.0" @@ -8,7 +8,7 @@ "browserslist": [ "defaults" ], - "repository": "https://github.com/artemiscloud/artemiscloud.github.io", + "repository": "https://github.com/arkmq-org/arkmq-org.github.io", "license": "MIT", "publishConfig": { "access": "public" diff --git a/static/arkmq.png b/static/arkmq.png new file mode 100644 index 0000000..ab2cb80 Binary files /dev/null and b/static/arkmq.png differ diff --git a/static/artemiscloud.svg b/static/arkmq.svg similarity index 96% rename from static/artemiscloud.svg rename to static/arkmq.svg index 9d74ebe..4f35c6a 100644 --- a/static/artemiscloud.svg +++ b/static/arkmq.svg @@ -13,9 +13,9 @@ height="18px" version="1.1" id="svg80" - sodipodi:docname="artemiscloudlogo.svg" + sodipodi:docname="arkmqlogo.svg" inkscape:version="1.0.2 (e86c870879, 2021-01-15)" - inkscape:export-filename="/home/dbruscin/Downloads/artemiscloudlogo.png" + inkscape:export-filename="/home/dbruscin/Downloads/arkmqlogo.png" inkscape:export-xdpi="96" inkscape:export-ydpi="96">