I am install MySQL HA follow by this doc:
./helm install report incubator/mysqlha -n middleware
but the result like this:
[dolphin#MeowK8SMaster1 linux-amd64]$ ./helm repo update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "traefik" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈ Happy Helming!⎈
[dolphin#MeowK8SMaster1 linux-amd64]$ ./helm install report incubator/mysqlha -n middleware
Error: failed to download "incubator/mysqlha" (hint: running `helm repo update` may help)
[dolphin#MeowK8SMaster1 linux-amd64]$
what should I do install mysql HA?
Your must first install the repository on which the mysqlh chart resides:
helm repo add incubator https://kubernetes-charts-incubator.storage.googleapis.com
Then run helm repo update. After that installation should succeed.
When unsure where to find helm chart repos, check Helm Hub: https://hub.helm.sh/charts/incubator/mysqlha
From the docs enable incubator repository
helm repo add incubator https://kubernetes-charts-incubator.storage.googleapis.com
And then run helm repo update followed by install
./helm install report incubator/mysqlha -n middleware
add incubator repo:
helm repo add incubator https://kubernetes-charts-incubator.storage.googleapis.com
Related
I have uploaded a helm chart as an OCI compliant container to Openshift. However, I can't add the openshift registry as a helm repo, or find another way to persuade helm to use the "imagestream" as a source to install.
export HELM_EXPERIMENTAL_OCI=1
oc whoami --show-token | helm registry login my-cluster.com -u $(oc whoami) --password-stdin
helm create mychart
cd mychart/
helm chart save . my-cluster.com/$(oc project -q)/mychart:latest
helm chart push my-cluster.com/$(oc project -q)/mychart:latest
And that creates a "mychart" imagestream with a dockerImageManifestMediaType: application/vnd.oci.image.manifest.v1+json
But whenever I try to add my-cluster.com as a repo or install any other way, it just gives me a 404 error :
helm install --username $(oc whoami) --password $(oc whoami --show-token) --repo https://my-cluster.com/$(oc project -q) mychart chart
Error: looks like "https://my-cluster.com/project" is not a valid chart repository or cannot be reached: failed to fetch https://my-cluster.com/project/index.yaml : 404 Not Found
Would it require the registry to do something "clever" to create the index.yaml which is missing in Openshift registry?
a helm chart is not the same as an OCI compliant container!
a helm chart basically is a compressed directory which a specified layout.
However, it is possible to host a chartmuseum on openshift, push your charts to said chartmuseum and then add it as a helm repository.
see the chartmuseum github repository for more information on how to host your own chartmuseum and this tutorial on how the chart should look like exactly and how to push it to your hosted chartmuseum.
I figured out you need to do :
helm chart pull registry/mychart:tag
helm chart export registry/mychart:tag .
So that your chart is in the current directory. And then you can :
helm install release mychart
There is a PR for future versions of helm to do a install of something like oci://registry/mychart:tag saving a few steps. I suppose this is the difference between registry and repository that was causing me problems.
Absolutely no need for chartmuseum or other third party apps.
I want to install mysql v8 with ansible by downloading repo ( mysql-apt-config_0.8.15-1_all.deb )
and install it with dpkg,when i want to manually without ansible install, it prompts a window to choose version and some configs and then i should click ok for adding the repo and updating the apt repo and so on
The problem comes in when i want to install repo and mysql package with ansible
Now how can i do this and solve my problem with prompt window in ansible?
Thanks for your answer.
I am trying to use bitbucket pipelines for my project, and i use simple config:
image: phpunit/phpunit:5.0.3
pipelines:
default:
- step:
script: # Modify the commands below to build your repository.
- composer --version
- phpunit --version
- composer global require "fxp/composer-asset-plugin:^1.2.0"
- composer install
- php init --env=Development --overwrite=All
But, at composer intall stage, i needs a github token, because yii2 is on github.
So, how to run composer with token, using this config ?
It should be enough to set some configuration for Composer. A link what command(s) to use: API rate limit and OAuth tokens. Simple steps:
Create an account on Github. You will get something like acd276d00a9de5a15743b7a0a33e39c0e7b8aed8. Be sure to make a note as you will not be able to look at it after some time.
Use Composer terminal (Git, for example) and enter command:
composer config -g github-oauth.github.com <oauthtoken>
Where <oauthtoken> is your token.
It should be configured now and Composer should now allow you to install.
I have installed Cygnus and I have it properly running with MYSQL. I would like to send the data which arrive to Cygnus through the notifications from Orion Context Broker, to a REST server.
I need to create a new Sink that processes the data that come from Orion, create the POST requests and run them. In order to do this, I have to create new Java files and I have to put these files in (according to "Adding new sinks development guide"):
fiware-connectors/flume/src/main/java/es/tid/fiware/fiwareconnectors/cygnus/sinks
and:
fiware-connectors/flume/src/main/java/es/tid/fiware/fiwareconnectors/cygnus/backends/<my_backend_classes>/
But I can not find these places. I installed Cygnus through the yum install command, so I do not know how to locate the places where I have to place these new java files.
Could you help me with this? Thanks in advance
Installing Cygnus by RPM will not install the sources. For that, you have to clone the Github repo (the git tool must be installed as well):
$ git clone https://github.com/telefonicaid/fiware-cygnus.git
That will clone the master branch, which is currently synchronized with the release 0.7.1.
Then, once you have added your new sink, you will have to build and install Cygnus from sources (your altered ones) as explained here.
I'v made a static single page site using grunt. I'm now trying to deploy it to heroku using the heroku-buildpack-nodejs-grunt for node grunt.
Below is a pic of my root directory:
Here's my Gruntfile package.json:
Procfile:
web: node index.html
When I run $ git push heroku master it gets to the Gruntfile and fails:
-----> Found Gruntfile, running grunt heroku:production task
>> Local Npm module "grunt-contrib-uglify" not found. Is it installed?
The above errors proceed to list all local NPM modules as not found. If I list all loadNpmTasks instead of using "load-grunt-tasks", I get the exact same error.
When I $ heroku logs I get:
Starting process with command `node web.js`
Error: Cannot find module '/app/web.js'
Can anyone see where I've gone wrong?
For anyone passing by here, I wasn't able to solve the problem. This is where I got to:
In my Gruntfile, I moved npm modules from devDependencies to dependencies. Heroku was then able to install these dependencies.
However, when Heroku ran the tasks, it stops at the haml task w/ error "You need to have Ruby and Haml installed and in your PATH for this task to work". Adding ruby & haml to the Gruntfile as engines did not work.
The only thing I can think of is that maybe Heroku installs your devDependencies first, tries to run Grunt, but since it didn't install load-grunt-tasks yet, you don't get the grunt.loadNpmTasks( 'grunt-contrib-uglify' ); line (which load-grunt-tasks does for you), and thus Grunt can't find the package.
Can you try changing your Gruntfile to explicitly list out all npm modules using the grunt.loadNpmTasks() method?
EDIT:
Just remembered another thing I had to do:
heroku labs:enable user-env-compile -a myapp
heroku config:set NODE_ENV=production
(Obviously replacing myapp with your Heroku app name.)
This makes Heroku allow user set environment variables and then sets your server to production. Try that, and set your dependencies and devDependencies as you had them originally (just to see if it works).
I am coming pretty late to the game here but I have used a couple methods and thought I would share.
Option 1: Get Heroku to Build
This is not my favorite method because it can take a long time but here it is anyway.
Heroku runs npm install --production when it receives your pushed changes. This only installs the production dependencies.
You don't have to change your environment variables to install your dev dependencies. npm install has a --dev switch to allow you to do that.
npm install --dev
Heroku provides an article on how you can customize your build. Essentially, you can run the above command as a postinstall script in your package.json.
"scripts": {
"start": "node index.js",
"postinstall": "npm install --dev && grunt build"
}
I think this is cleaner than putting dev dependencies in my production section or changing the environment variables back and forth to get my dependencies to build.
Also, I don't use a Procfile. Heroku can run your application by calling npm start (at least it can now almost two years after the OP). So as long as you provide that script (as seen above) Heroku should be able to start your app.
As far as your ruby dependency, I haven't attempted to install a ruby gem in my node apps on Heroku but this SO answer suggests that you use multi buildpack.
Option 2: Deploy Your Dependencies
Some argue that having Heroku build your application is bad form. They suggest that you should push up all of your dependencies. If you are like me and hate the idea of checking in your node_modules directory then you could create a new branch where you force add the node_modules directory and then deploy that branch. In git this looks like:
git checkout -b deploy
git add -f node_modules/
git commit -m "heroku deploy"
git push heroku --force deploy:master
git checkout master
git branch -D deploy
You could obviously make this into a script so that you don't have to type that every time.
Option 3: Do It All Yourself
This is my new favorite way to deploy. Heroku has added support for slug deploys. The previous link is a good read and I highly recommend it. I do this in my automated build from Travis-CI. I have some custom scripts to tar my app and push the slug to Heroku and its fast.
I faced a similar problem with Heroku not installing all of my dependencies, while I had no issue locally. I fixed it by running
heroku config:set USE_NPM_INSTALL=true
into the path, where I deployed my project from. This instructs Heroku to install your dependencies using npm install instead of npm ci, which is the default! From Heroku dev center:
"Heroku uses the lockfiles, either the package-lock.json or yarn.lock, to install the expected dependency tree, so be sure to check those files into git to ensure the same dependency versions across environments. If you are using npm, Heroku will use npm ci to set up the build environment."