diff --git a/.github/ISSUE_TEMPLATE/bug-report.md b/.github/ISSUE_TEMPLATE/bug-report.md
index 51d0c6f93e..eefcfe3702 100644
--- a/.github/ISSUE_TEMPLATE/bug-report.md
+++ b/.github/ISSUE_TEMPLATE/bug-report.md
@@ -1,15 +1,14 @@
---
name: Bug Report
-about: Report a bug encountered while operating Microshift
+about: Report a bug encountered while operating MicroShift
labels: bug
-title: '[BUG]
'
-
+title: "[BUG] "
+modified: "2021-10-27T12:41:31.324+02:00"
---
-
#### What happened:
#### What you expected to happen:
@@ -21,14 +20,12 @@ title: '[BUG] '
#### Anything else we need to know?:
-
#### Environment:
-- Microshift version (use `microshift version`):
+
+- MicroShift version (use `microshift version`):
- Hardware configuration:
- OS (e.g: `cat /etc/os-release`):
- Kernel (e.g. `uname -a`):
- Others:
-#### Relevant Logs
-
-
+#### Relevant Logs
diff --git a/.github/ISSUE_TEMPLATE/enhancement-tracking.md b/.github/ISSUE_TEMPLATE/enhancement-tracking.md
index 8ba092cf32..468fcf191c 100644
--- a/.github/ISSUE_TEMPLATE/enhancement-tracking.md
+++ b/.github/ISSUE_TEMPLATE/enhancement-tracking.md
@@ -2,14 +2,15 @@
name: Enhancement Tracking Issue
about: Provide supporting details for a feature in development
labels: feature
-title: '[Enhancement]: '
-
+title: "[Enhancement]: "
---
+
+
#### Design Document Link
PR: #
@@ -17,5 +18,3 @@ PR: #
#### What would you like to be added:
#### Why is this needed:
-
-
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index e2462808c8..257414eb53 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -2,9 +2,12 @@
If this is your first contribution, read our Contributing guide https://github.com/redhat-et/microshift/CONTRIBUTING.md
If the PR is not yet ready for review, prefix [WIP] in the title. Once prepared, remote the prefix.
-->
+
**Which issue(s) this PR addresses**:
+
+
Closes #
diff --git a/.github/workflows/nightly.yaml b/.github/workflows/nightly.yaml
index 70f443ec67..ec8627bfb4 100644
--- a/.github/workflows/nightly.yaml
+++ b/.github/workflows/nightly.yaml
@@ -12,7 +12,7 @@ jobs:
uses: actions/checkout@v2
- name: Install required packages
- run: sudo apt install build-essential qemu-user qemu-user-static
+ run: sudo apt install build-essential qemu-user qemu-user-static
- name: launch build
run: make build-containerized-cross-build
@@ -37,4 +37,4 @@ jobs:
files: |
microshift-linux-amd64
microshift-linux-arm64
- release.sha256
\ No newline at end of file
+ release.sha256
diff --git a/.github/workflows/release.yaml b/.github/workflows/release.yaml
index 0f3378ef46..e74eae326d 100644
--- a/.github/workflows/release.yaml
+++ b/.github/workflows/release.yaml
@@ -20,13 +20,13 @@ jobs:
password: ${{ secrets.REGISTRY_PASS }}
- name: Install required packages
- run: sudo apt install build-essential qemu-user qemu-user-static
-
+ run: sudo apt install build-essential qemu-user qemu-user-static
+
- name: Checkout source
uses: actions/checkout@v2
-
+
- name: execute release.sh
shell: bash
run: make release TOKEN=${GITHUB_TOKEN}
env:
- GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
\ No newline at end of file
+ GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
diff --git a/.github/workflows/ubuntu.yaml b/.github/workflows/ubuntu.yaml
index dcbd3dd7d7..56b590f86f 100644
--- a/.github/workflows/ubuntu.yaml
+++ b/.github/workflows/ubuntu.yaml
@@ -23,7 +23,7 @@ jobs:
run: sudo apt install build-essential
- name: Checkout
- uses: actions/checkout@v2
+ uses: actions/checkout@v2
- name: make
run: make build
@@ -33,7 +33,7 @@ jobs:
with:
name: microshift
path: ./microshift
-
+
deploy-microshift:
name: Deploy-Microshift
needs: Build-Microshift
@@ -43,7 +43,7 @@ jobs:
steps:
- name: Checkout
uses: actions/checkout@v2
-
+
- name: download archive
uses: actions/download-artifact@v2.0.10
with:
@@ -51,7 +51,7 @@ jobs:
path: /tmp/
- name: sleep then run kubectl
- run: chmod +x /tmp/microshift
+ run: chmod +x /tmp/microshift
- name: install script
run: CONFIG_ENV_ONLY=true ./install.sh
@@ -64,4 +64,4 @@ jobs:
sudo -i sh -c 'until [ -f /var/lib/microshift/resources/kubeadmin/kubeconfig ]; do sudo sleep 5; done'
sudo cp /var/lib/microshift/resources/kubeadmin/kubeconfig /tmp/kubeconfig
sudo chown `whoami`: /tmp/kubeconfig
- make test-e2e
+ make test-e2e
diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
new file mode 100644
index 0000000000..0f9df8c3b4
--- /dev/null
+++ b/.pre-commit-config.yaml
@@ -0,0 +1,93 @@
+fail_fast: true
+exclude: ^vendor/|^features/|^scripts/rebase_patches/
+repos:
+ - repo: meta
+ hooks:
+ - id: check-useless-excludes
+ - repo: https://github.com/asottile/pyupgrade
+ rev: v2.29.0
+ hooks:
+ - id: pyupgrade
+ args: [--py39-plus]
+ - repo: https://github.com/pre-commit/mirrors-prettier
+ rev: v2.4.1
+ hooks:
+ - id: prettier
+ files: \.(css|js|md|markdown|json)
+ - repo: https://github.com/asottile/seed-isort-config
+ rev: v2.2.0
+ hooks:
+ - id: seed-isort-config
+ - repo: https://github.com/pre-commit/mirrors-isort
+ rev: v5.9.3
+ hooks:
+ - id: isort
+ - repo: https://github.com/python/black
+ rev: 21.6b0
+ hooks:
+ - id: black
+ - repo: https://github.com/pre-commit/pre-commit-hooks
+ rev: v4.0.1
+ hooks:
+ - id: check-added-large-files
+ args: ["--maxkb=10000"]
+ - id: check-ast
+ - id: check-case-conflict
+ - id: check-executables-have-shebangs
+ - id: check-json
+ - id: check-merge-conflict
+ - id: check-symlinks
+ # - id: check-vcs-permalinks
+ - id: debug-statements # Check for debugger imports and py37+ `breakpoint()` calls in python source.
+ - id: check-xml
+ - id: check-yaml
+ args:
+ - --unsafe
+ - id: end-of-file-fixer
+ - id: forbid-new-submodules
+ - id: no-commit-to-branch
+ args:
+ - --branch
+ - gh-pages
+ - id: requirements-txt-fixer
+ - id: sort-simple-yaml
+ - id: trailing-whitespace
+ - id: mixed-line-ending
+ - id: detect-private-key
+ - id: check-byte-order-marker
+ - id: check-docstring-first
+ # - id: detect-aws-credentials
+ # - id: fix-encoding-pragma
+ - repo: https://gitlab.com/pycqa/flake8
+ rev: 3.9.2
+ hooks:
+ - id: flake8
+ - repo: local
+ hooks:
+ - id: shfmt
+ name: shfmt
+ minimum_pre_commit_version: 2.4.0
+ language: golang
+ additional_dependencies:
+ - mvdan.cc/sh/v3/cmd/shfmt@v3.1.1
+ entry: shfmt
+ args:
+ - -w
+ - -i
+ - "4"
+ types:
+ - shell
+ - repo: https://github.com/asottile/blacken-docs
+ rev: v1.11.0
+ hooks:
+ - id: blacken-docs
+ - repo: https://github.com/hcodes/yaspeller.git
+ rev: v7.2.0
+ hooks:
+ - id: yaspeller
+ types:
+ - markdown
+ # - repo: https://github.com/pre-commit/mirrors-mypy
+ # rev: v0.910
+ # hooks:
+ # - id: mypy
diff --git a/.yaspeller.json b/.yaspeller.json
new file mode 100644
index 0000000000..19b6320f50
--- /dev/null
+++ b/.yaspeller.json
@@ -0,0 +1,62 @@
+{
+ "ignoreUrls": true,
+ "findRepeatWords": true,
+ "maxRequests": 5,
+ "ignoreDigits": true,
+ "lang": "en",
+ "dictionary": [
+ "KUBECONFIG",
+ "MicroShift",
+ "NetworkManager",
+ "OpenShift",
+ "podman",
+ "RHEL",
+ "systemd",
+ "toc",
+ "workaround",
+ "Andrés",
+ "VM",
+ "Virtualization",
+ "hostname",
+ "VSCode",
+ "dropdown",
+ "OKD",
+ "IoT",
+ "LTE",
+ "Kubernetes",
+ "MicroShift's",
+ "lifecycle",
+ "SELinux",
+ "MacOS",
+ "GPU",
+ "CentOS",
+ "CRI-O",
+ "Non-OKD",
+ "non-OKD",
+ "endraw",
+ "endcomment",
+ "AIO",
+ "µShift",
+ "barebone",
+ "seamlessly",
+ "resp",
+ "firewalled",
+ "LBN",
+ "GW",
+ "OKD's",
+ "CVE",
+ "SemVer",
+ "STIG",
+ "CI",
+ "DISA",
+ "FedRAMP",
+ "versioning",
+ "CSI",
+ "NAT",
+ "rebasing",
+ "deployable",
+ "personas",
+ "dongle",
+ "NAT'ed"
+ ]
+}
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 63d21c91b6..03d583ae82 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,3 +1,7 @@
+---
+modified: "2021-10-27T12:18:27.143+02:00"
+---
+
# Contributing to MicroShift
If you would like to develop MicroShift locally, you can follow this guide on getting
@@ -5,23 +9,19 @@ it installed and running through the provided Makefile.
This guide will primarily focus on running MicroShift within a VM using Vagrant.
-
## (optional) Developing with Vagrant
To get started with development, it is recommended to use Vagrant for VM provisioning,
however it is not necessary.
-You can find a guide on how to install it for your system [here](https://www.vagrantup.com/downloads).
+You can find a guide on how to install it for your system [here](https://www.vagrantup.com/downloads).
Once Vagrant is installed, you will need to create a Vagrant box for the operating
system of your choice. For this example we will be looking at a [fedora 34 cloud
image](https://app.vagrantup.com/fedora/boxes/34-cloud-base), however you can substitute any vagrant image of your choice.
-
First, navigate to the MicroShift directory on your host system, or another designated
-directory where we will be storing the Vagrantfile.
-
-
+directory where we will be storing the `Vagrantfile`.
Next, download the vagrant image. For this example we will use
a fedora 34 cloud image:
@@ -43,8 +43,9 @@ Running this command will create a `Vagrantfile` in your working directory which
is used to configure your vagrant box.
Before we start our Vagrant box, we will need to increase the amount of RAM available
-to the system.
-To do this, edit the Vagrantfile and configure your provider settings to include
+to the system.
+
+To do this, edit the `Vagrantfile` and configure your provider settings to include
the following:
```rb
@@ -57,10 +58,9 @@ the following:
```
The value of `config.vm.provider` depends on the provider you selected when you
-ran `vagrant add` earlier. For example, if you selected virtualbox then the first
+ran `vagrant add` earlier. For example, if you selected `virtualbox` then the first
line should be: `config.vm.provider "virtualbox" do |v|`
-
Now we can start the VM:
```
@@ -73,15 +73,15 @@ Once the VM is up, connect to it:
vagrant ssh
```
-### (Extra Optional) Connecting VSCode to Vagrant
+### (Extra Optional) Connecting VSCode to Vagrant
If you're using VSCode, you can connect to your vagrant box with a few extra steps.
#### Increasing Memory Requirements
-Since VS Code leans more on the heavy side of development, the RAM usage on your Vagrant environment
+Since VSCode leans more on the heavy side of development, the RAM usage on your Vagrant environment
can go up to 5GB, and therefore we will need to modify the `Vagrantfile` to
-increase the amount of available RAM from 3GB to 5GB (or 6GB if you want to be safe).
+increase the amount of available RAM from 3GB to 5GB (or 6GB if you want to be safe).
To do this, set `v.memory` to the following in your `Vagrantfile`:
```rb
@@ -99,10 +99,11 @@ First we need to ask Vagrant for an SSH config file. From your host machine, run
vagrant ssh-config > ssh-config.conf
```
-*You can edit the `ssh-config.conf` file to change the hostname from `default` to
-`vagrant` to be more easily identifiable, but that's up to you. :)*
+_You can edit the `ssh-config.conf` file to change the hostname from `default` to
+`vagrant` to be more easily identifiable, but that's up to you. :)_
Here's an example of my working SSH config file:
+
```
Host default
HostName 127.0.0.1
@@ -116,11 +117,8 @@ Host default
LogLevel FATAL
```
-
Next, you'll want to install the `Remote - SSH` extension from the [VSCode Marketplace](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-ssh)
-
-
With the extension installed, you'll click on the green bottom in the bottom-left
corner of VSCode to open a dropdown menu for SSH options:
@@ -133,28 +131,27 @@ Next you'll want to navigate to the "Remote Explorer" tab on the left-hand side
of VSCode, then select on the vagrant target (default if you haven't renamed it)
and click on the button to connect to it in a remote window.
-
-*(Credits to Andrés Lopez for this guide: [Connect Visual Studio Code with Vagrant in your local machine
-](https://medium.com/@lopezgand/connect-visual-studio-code-with-vagrant-in-your-local-machine-24903fb4a9de))*
-
+_(Credits to Andrés Lopez for this guide: [Connect Visual Studio Code with Vagrant in your local machine
+](https://medium.com/@lopezgand/connect-visual-studio-code-with-vagrant-in-your-local-machine-24903fb4a9de))_
## Running MicroShift Locally
### Pre-Installation
You will need to install the required binaries:
-- git
-- make
-- golang
-- glibc
-- podman
+
+- `git`
+- `make`
+- `golang`
+- `glibc`
+- `podman`
```sh
-# Fedora/CentOS
+# Fedora/CentOS
sudo dnf install \
git \
make \
- golang \
+ golang \
glibc-static
# Ubuntu
@@ -168,8 +165,8 @@ sudo apt install \
To install podman, you can find the appropriate guide for your respective system:
[Install Podman](https://podman.io/getting-started/installation)
+Next you'll want to clone the repository and `cd` into it:
-Next you'll want to clone the repository and cd into it:
```sh
git clone https://github.com/redhat-et/microshift.git
cd microshift
@@ -182,7 +179,5 @@ Now we can build MicroShift:
```sh
make build
CONFIG_ENV_ONLY=true ./install.sh
-sudo ./microshift run
+sudo ./microshift run
```
-
-
diff --git a/README.md b/README.md
index 9cf3d6b6df..e603420497 100644
--- a/README.md
+++ b/README.md
@@ -1,3 +1,7 @@
+---
+modified: "2021-10-29T08:27:16.055+02:00"
+---
+
# MicroShift
MicroShift is a research project that is exploring how OpenShift1 Kubernetes can be optimized for small form factor and edge computing.
@@ -27,8 +31,7 @@ In order to run MicroShift, you will need at least:
- ~124MB of free storage space for the MicroShift binary
- 64-bit CPU (although 32-bit is _technically_ possible, if you're up for the challenge)
-For barebones development the minimum requirement is 3GB of RAM, though this can increase
-if you are using resource-intensive devtools.
+For barebone development the minimum requirement is 3GB of RAM, though this can increase if you are using resource-intensive development tools.
### OS Requirements
@@ -46,7 +49,7 @@ It may be possible to run MicroShift on other systems, however they haven't been
## Using MicroShift
-To give MicroShift a try, simply install a recent test version (we don't provide stable releases yet) on a Fedora-derived Linux distro (we've only tested Fedora, RHEL, and CentOS Stream so far) using:
+To give MicroShift a try, simply install a recent test version (we don't provide stable releases yet) on a Fedora-derived Linux distribution (we've only tested Fedora, RHEL, and CentOS Stream so far) using:
```sh
curl -sfL https://raw.githubusercontent.com/redhat-et/microshift/main/install.sh | bash
@@ -54,7 +57,7 @@ curl -sfL https://raw.githubusercontent.com/redhat-et/microshift/main/install.sh
This will install MicroShift's dependencies (CRI-O), install it as a systemd service and start it.
-For convenience, the script will also add a new "microshift" context to your `$HOME/.kube/config`, so you'll be able to access your cluster using, e.g.:
+For convenience, the script will also add a new `microshift` context to your `$HOME/.kube/config`, so you'll be able to access your cluster using, e.g.:
```sh
kubectl get all -A --context microshift
@@ -72,16 +75,17 @@ Notes: When installing MicroShift on a system with an older version already inst
```sh
rm -rf /var/lib/microshift && rm -r $HOME/.microshift
```
+
## Deployment Strategies
In production environment MicroShift can be deployed as:
-1. Install via an RPM, utilizing a host-provided cri-o runtime and be lifecycle-managed by systemd
-2. [Install as a container via Podman, utilizing cri-o runtime and be lifecycle-managed by systemd](./docs/microshift-containerized/README.md)
+1. Install via an RPM, utilizing a host-provided `cri-o` runtime and be lifecycle-managed by systemd
+2. [Install as a container via Podman, utilizing `cri-o` runtime and be lifecycle-managed by systemd](./docs/microshift-containerized/README.md)
For app developer deployments:
-1. [Run an all-in-one microshift deployment on which devs can test their applications locally](.docs/microshift-aio/README.md). `microshift-aio` packages cri-o runtime and can be run and managed via podman and systemd
+1. [Run an all-in-one MicroShift deployment on which developers can test their applications locally](.docs/microshift-aio/README.md). `microshift-aio` packages `cri-o` runtime and can be run and managed via podman and systemd
## [Known Issues](./docs/known-issues.md)
@@ -91,7 +95,7 @@ For app developer deployments:
### Building
-You can locally build MicroShift using one of two methods, either using a container build (recommended) on Podman or Docker:
+You can locally build MicroShift using one of two methods, either using a container build (recommended) on `podman` or Docker:
```sh
sudo yum -y install make golang
@@ -120,18 +124,18 @@ Before running MicroShift, the host must first be configured. This can be handle
CONFIG_ENV_ONLY=true ./install.sh
```
-MicroShift keeps all its state in its data-dir, which defaults to `/var/lib/microshift` when running MicroShift as privileged user and `$HOME/.microshift` otherwise. Note that running MicroShift unprivileged only works without node role at the moment (i.e. using `--roles=controlplane` instead of the default of `--roles=controlplane,node`).
+MicroShift keeps all its state in its data directory, which defaults to `/var/lib/microshift` when running MicroShift as privileged user and `$HOME/.microshift` otherwise. Note that running MicroShift unprivileged only works without node role at the moment (i.e. using `--roles=controlplane` instead of the default of `--roles=controlplane,node`).
-### Kubeconfig
+### `Kubeconfig`
-When starting the MicroShift for the first time the Kubeconfig file is created. If you need it for another user or to use externally the kubeadmin's kubeconfig is placed at `/var/lib/microshift/resources/kubeadmin/kubeconfig`.
+When starting the MicroShift for the first time the `kubeconfig` file is created. If you need it for another user or to use externally the `kubeadmin`'s `kubeconfig` is placed at `/var/lib/microshift/resources/kubeadmin/kubeconfig`.
### Contributing
-For more information on working with MicroShift, you can find a contributor's guide in [CONTRIBUTING.md](./CONTRIBUTING.md)
+For more information on working with MicroShift, you can find a contributor's guide in [`CONTRIBUTING.md`](./CONTRIBUTING.md)
### Community
-Join us on [Slack](https://microshift.slack.com)! ([Invite to the Slack space](https://join.slack.com/t/microshift/shared_invite/zt-uxncbjbl-XOjueb1ShNP7xfByDxNaaA))
+Join us on [Slack](https://MicroShift.slack.com)! ([Invite to the Slack space](https://join.slack.com/t/MicroShift/shared_invite/zt-uxncbjbl-XOjueb1ShNP7xfByDxNaaA))
Community meetings are held weekly, Wednesdays at 10:30AM - 11:00AM EST. Be sure to join the community [calendar](https://calendar.google.com/calendar/embed?src=nj6l882mfe4d2g9nr1h7avgrcs%40group.calendar.google.com&ctz=America%2FChicago)! Click "Google Calendar" in the lower right-hand corner to subscribe.
diff --git a/assets/apps/0000_00_flannel-daemonset.yaml b/assets/apps/0000_00_flannel-daemonset.yaml
index 457205a1ba..e9017cdb4a 100644
--- a/assets/apps/0000_00_flannel-daemonset.yaml
+++ b/assets/apps/0000_00_flannel-daemonset.yaml
@@ -87,4 +87,4 @@ spec:
path: /etc/cni/net.d
- name: flannel-cfg
configMap:
- name: kube-flannel-cfg
\ No newline at end of file
+ name: kube-flannel-cfg
diff --git a/assets/apps/0000_70_dns_01-dns-daemonset.yaml b/assets/apps/0000_70_dns_01-dns-daemonset.yaml
index 9c635d3df3..b6a47f48d0 100644
--- a/assets/apps/0000_70_dns_01-dns-daemonset.yaml
+++ b/assets/apps/0000_70_dns_01-dns-daemonset.yaml
@@ -81,7 +81,7 @@ spec:
readOnly: true
dnsPolicy: Default
nodeSelector:
- kubernetes.io/os: linux
+ kubernetes.io/os: linux
volumes:
- name: config-volume
configMap:
diff --git a/assets/core/0000_00_flannel-configmap.yaml b/assets/core/0000_00_flannel-configmap.yaml
index 7a0750c6c2..9d72ff3e2d 100644
--- a/assets/core/0000_00_flannel-configmap.yaml
+++ b/assets/core/0000_00_flannel-configmap.yaml
@@ -33,4 +33,4 @@ data:
"Backend": {
"Type": "vxlan"
}
- }
\ No newline at end of file
+ }
diff --git a/assets/core/0000_00_flannel-service-account.yaml b/assets/core/0000_00_flannel-service-account.yaml
index c731020846..7c0411b161 100644
--- a/assets/core/0000_00_flannel-service-account.yaml
+++ b/assets/core/0000_00_flannel-service-account.yaml
@@ -2,4 +2,4 @@ apiVersion: v1
kind: ServiceAccount
metadata:
name: flannel
- namespace: kube-system
\ No newline at end of file
+ namespace: kube-system
diff --git a/assets/core/0000_80_hostpath-provisioner-namespace.yaml b/assets/core/0000_80_hostpath-provisioner-namespace.yaml
index fe8e57079b..4048a355ae 100644
--- a/assets/core/0000_80_hostpath-provisioner-namespace.yaml
+++ b/assets/core/0000_80_hostpath-provisioner-namespace.yaml
@@ -1,4 +1,4 @@
apiVersion: v1
kind: Namespace
metadata:
- name: kubevirt-hostpath-provisioner
\ No newline at end of file
+ name: kubevirt-hostpath-provisioner
diff --git a/assets/core/0000_80_hostpath-provisioner-serviceaccount.yaml b/assets/core/0000_80_hostpath-provisioner-serviceaccount.yaml
index eb1a9735dc..0e3fd608ef 100644
--- a/assets/core/0000_80_hostpath-provisioner-serviceaccount.yaml
+++ b/assets/core/0000_80_hostpath-provisioner-serviceaccount.yaml
@@ -2,4 +2,4 @@ apiVersion: v1
kind: ServiceAccount
metadata:
name: kubevirt-hostpath-provisioner-admin
- namespace: kubevirt-hostpath-provisioner
\ No newline at end of file
+ namespace: kubevirt-hostpath-provisioner
diff --git a/assets/core/0000_80_openshift-router-cm.yaml b/assets/core/0000_80_openshift-router-cm.yaml
index 01ae4ed455..3afde8c89c 100644
--- a/assets/core/0000_80_openshift-router-cm.yaml
+++ b/assets/core/0000_80_openshift-router-cm.yaml
@@ -2,6 +2,6 @@ apiVersion: v1
kind: ConfigMap
metadata:
namespace: openshift-ingress
- name: service-ca-bundle
+ name: service-ca-bundle
annotations:
service.beta.openshift.io/inject-cabundle: "true"
diff --git a/assets/core/0000_80_openshift-router-external-service.yaml b/assets/core/0000_80_openshift-router-external-service.yaml
index d95198fcfc..4ace806cae 100644
--- a/assets/core/0000_80_openshift-router-external-service.yaml
+++ b/assets/core/0000_80_openshift-router-external-service.yaml
@@ -10,7 +10,7 @@ metadata:
spec:
selector:
ingresscontroller.operator.openshift.io/deployment-ingresscontroller: default
- type: NodePort
+ type: NodePort
ports:
- name: http
port: 80
diff --git a/assets/rbac/0000_00_flannel-clusterrole.yaml b/assets/rbac/0000_00_flannel-clusterrole.yaml
index 8e30979418..dc07eb8095 100644
--- a/assets/rbac/0000_00_flannel-clusterrole.yaml
+++ b/assets/rbac/0000_00_flannel-clusterrole.yaml
@@ -25,4 +25,4 @@ rules:
resources:
- nodes/status
verbs:
- - patch
\ No newline at end of file
+ - patch
diff --git a/assets/rbac/0000_00_flannel-clusterrolebinding.yaml b/assets/rbac/0000_00_flannel-clusterrolebinding.yaml
index fa4a4ec4d7..9021d11fa5 100644
--- a/assets/rbac/0000_00_flannel-clusterrolebinding.yaml
+++ b/assets/rbac/0000_00_flannel-clusterrolebinding.yaml
@@ -9,4 +9,4 @@ roleRef:
subjects:
- kind: ServiceAccount
name: flannel
- namespace: kube-system
\ No newline at end of file
+ namespace: kube-system
diff --git a/assets/rbac/0000_00_podsecuritypolicy-flannel.yaml b/assets/rbac/0000_00_podsecuritypolicy-flannel.yaml
index 04e8be18d3..137641209a 100644
--- a/assets/rbac/0000_00_podsecuritypolicy-flannel.yaml
+++ b/assets/rbac/0000_00_podsecuritypolicy-flannel.yaml
@@ -43,4 +43,4 @@ spec:
# SELinux
seLinux:
# SELinux is unused in CaaSP
- rule: 'RunAsAny'
\ No newline at end of file
+ rule: 'RunAsAny'
diff --git a/assets/rbac/0000_60_service-ca_00_role.yaml b/assets/rbac/0000_60_service-ca_00_role.yaml
index 049106e265..617eb18e44 100644
--- a/assets/rbac/0000_60_service-ca_00_role.yaml
+++ b/assets/rbac/0000_60_service-ca_00_role.yaml
@@ -44,4 +44,4 @@ rules:
verbs:
- get
- list
- - watch
\ No newline at end of file
+ - watch
diff --git a/assets/rbac/0000_80_hostpath-provisioner-clusterrolebinding.yaml b/assets/rbac/0000_80_hostpath-provisioner-clusterrolebinding.yaml
index 7102060276..7c5e26f8ed 100644
--- a/assets/rbac/0000_80_hostpath-provisioner-clusterrolebinding.yaml
+++ b/assets/rbac/0000_80_hostpath-provisioner-clusterrolebinding.yaml
@@ -9,4 +9,4 @@ subjects:
roleRef:
kind: ClusterRole
name: kubevirt-hostpath-provisioner
- apiGroup: rbac.authorization.k8s.io
\ No newline at end of file
+ apiGroup: rbac.authorization.k8s.io
diff --git a/assets/storage/0000_80_hostpath-provisioner-storageclass.yaml b/assets/storage/0000_80_hostpath-provisioner-storageclass.yaml
index 732978ff9e..ed38597a4e 100644
--- a/assets/storage/0000_80_hostpath-provisioner-storageclass.yaml
+++ b/assets/storage/0000_80_hostpath-provisioner-storageclass.yaml
@@ -4,4 +4,4 @@ metadata:
name: kubevirt-hostpath-provisioner
provisioner: kubevirt.io/hostpath-provisioner
reclaimPolicy: Delete
-volumeBindingMode: WaitForFirstConsumer
\ No newline at end of file
+volumeBindingMode: WaitForFirstConsumer
diff --git a/docs/.gitignore b/docs/.gitignore
index dd6b60552f..291f0817f1 100644
--- a/docs/.gitignore
+++ b/docs/.gitignore
@@ -1,4 +1,3 @@
vendor/**
_site/**
Gemfile.lock
-
diff --git a/docs/Gemfile b/docs/Gemfile
old mode 100755
new mode 100644
diff --git a/docs/_layouts/default.html b/docs/_layouts/default.html
index efcda1b46c..3573433f41 100644
--- a/docs/_layouts/default.html
+++ b/docs/_layouts/default.html
@@ -27,4 +27,4 @@
{%- include footer.html -%}