What exactly is Helm of Brilliance’s “a sword of flame” power?

I don’t have the exact AD&D 2nd edition Dungeon Master’s Guide quote, but there is an item, Helm of Brilliance, which, among other things, allows the wearer to turn any sword to a sword of flame.

What is “a sword of flame” here, and more importantly where in the official rule books is it described?

If it isn’t actually described anywhere, is there any less official source on what this power of the Helm actually does? I’m looking for something to show to my DM.

How does the Helm of Brilliance interact with Great Weapon Fighting?

The item Helm of Brilliance includes a feature that reads:

You can use an action and speak a Command Word to cause one weapon you are holding to burst into flames. […] When you hit with an Attack using the blazing weapon, the target takes an extra 1d6 fire damage. (DMG, 173)

Great Weapon Fighting reads:

When you roll a 1 or 2 on a damage die for an attack you make with a melee weapon that you are wielding with two hands, you can reroll the die and must use the new roll, even if the new roll is a 1 or a 2. (PHB, 72)

This question deals with what dice are affected by Great Weapon Fighting and it seems that the the feature was only intended to affect the weapons damage dice not extra dice from features like Sneak Attack or Divine Smite, or spells such as Hex. It seems that all of the weapon’s damage die, however, are affected and so weapons such as Frost Brand have their additional dice modified (1d6 cold damage in the case of Frost Brand).

In the case of Helm of Brilliance‘s flame effect does is the additional 1d6 fire damage affected by Great Weapon Fighting?

On one hand it seems like no because it is clearly a spell like effect rather than a natural part of the weapon. On the other hand the effect clearly modifies the weapon rather than the attack and so the additional damage could be considered a quality of the weapon.

Can an undead creature like Strahd wield a Helm of Brilliance?

I had a thought that if my players don’t raid the treasury before their fight with Strahd, he would use the magic items inside during the final fight against the players. However…

The description for the Helm of Brilliance mentions that:

  • As long as it has at least one diamond, the helm emits dim light in a 30-foot radius when at least one undead is within that area. Any undead that starts its turn in that area takes 1d6 radiant damage.

Since wearing the helmet technically means being within the effects radius…

  • Does this mean Strahd would be damaged by the helm if he got anywhere near it, even if it was lying on the floor un-attuned?
  • Could he pluck out all the diamonds before the fight to eliminate this potential threat, or would it burn his hands or something similar?
  • Could any undead creature wear the helm of brilliance without it dealing damage to said wearer?

Helm Chart loads default Laravel instead of real site

I have set up my project to use this package for Kubernetes/Helm on Laravel application: https://github.com/richdynamix/arc

When I run

docker-compose up 

I get the real project I have been working on, but when I install Helm at tools/helm-chart folder using this command:

helm install . 

I get the default laravel startup page, not the real project I have been working on.

Steps I have made:

  1. Test with docker-compose up
  2. Push to private docker repo using

    docker push myusername/reponame:latest

  3. Setup helm chart details and docker user/pass at tools/helm-chart/values.yaml

  4. Run

    helm install .

  5. Visit deployed website to see its not working properly.

I have tested this on Google Cloud and locally. Same result.

Any ideas what might be wrong here?

How to add extraScrapeConfigs to Prometheus helm chart from –set argument?

I want to deploy Prometheus from the official helm chart on the stable repo.

Also, I want to add my own scrape config.

I can successfully add extra configs directly from the values.yml file of the chart, after downloading and altering it, but when I try to pass it as argument with --set nothing happens.

This works [in values.yml]:

# adds additional scrape configs to prometheus.yml # must be a string so you have to add a | after extraScrapeConfigs: # example adds prometheus-blackbox-exporter scrape config extraScrapeConfigs: |   - job_name: 'sample-job'     scrape_interval: 1s     metrics_path: /     kubernetes_sd_configs:       - role: endpoints 

this does not:

sudo helm upgrade --install prometheus \ --set rbac.create=true \ --set server.persistentVolume.enabled=false \ --set alertmanager.persistentVolume.enabled=false \ --set alertmanager.enabled=false \ --set kubeStateMetrics.enabled=false \ --set nodeExporter.enabled=false \ --set pushgateway.enabled=false \ --set extraScrapeConfigs="|   - job_name: 'sample-pods'     scrape_interval: 1s     metrics_path: /     kubernetes_sd_configs:       - role: endpoints " \ stable/prometheus 

Is it possible someway?

I found this SO question How to use –set to set values with Prometheus chart? , but I cannot find a way to apply it to my case.

Helm under MicroK8S giving: “Error: could not find a ready tiller pod”

On a fresh install of [Ubuntu 18.04.2 Server X64] Im installing MicroK8S and Helm with the commands:

       sudo snap install microk8s --classic        microk8s.kubectl version        alias kubectl='microk8s.kubectl'        alias docker='microk8s.docker'        kubectl describe nodes | egrep 'Name:|Roles:|Taints:'             Name:   myServerName             Roles:  <none>             Taints: node.kubernetes.io/disk-pressure:NoSchedule        kubectl taint nodes --all node-role.kubernetes.io/master-             Error: taint "node-role.kubernetes.io/master:" not found        kubectl get nodes        sudo snap install helm --classic        helm init        helm version             Error: could not find a ready tiller pod                   helm ls             Error: could not find a ready tiller pod 

As you can see its giving the error:

            Error: could not find a ready tiller pod            

And I did the FIX on https://stackoverflow.com/a/49764370 as you can see above.

There is an ISSUE opened on Github pointing to FIX above and closing as solved but it dont solve.

Error trying to install Helm chart on a DigitalOcean Kubernetes Cluster

I’m following this guide to install and setup the Helm Dashboard on a Digital Ocean Kubernetes Cluster.

I can get as far as this command:

helm install stable/kubernetes-dashboard --name dashboard-demo 

and then I get this error:

Error: release dashboard-demo failed: namespaces “default” is forbidden: User “system:serviceaccount:kube-system:default” cannot get resource “namespaces” in API group “” in the namespace “default”

Any ideas what I need to do to fix this or should I raise a ticket on DO?